Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 5095313232c15aa3011fdb064f8cd78eff201b969b770203a620e818c3a3a32d

Tx prefix hash: 0ca28114e8e4dafd702f1232a79b9d00823f0216f08dbc5766bf243717d17a25
Tx public key: 57c20da03bcfe5dfec1f726c23f97b1e2002e30a2e64a3248d6bfacd3b2ec991
Timestamp: 1577017132 Timestamp [UCT]: 2019-12-22 12:18:52 Age [y:d:h:m:s]: 04:320:03:00:37
Block: 29623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117548 RingCT/type: yes/0
Extra: 0157c20da03bcfe5dfec1f726c23f97b1e2002e30a2e64a3248d6bfacd3b2ec9910211000000128a2ee0d9000000000000000000

1 output(s) for total of 489.606941801000 dcy

stealth address amount amount idx
00: 81b31f46449e4021f17399d8eb191cadc78314198126b69275c40554f3f22af6 489.606941801000 48741 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 29633, "vin": [ { "gen": { "height": 29623 } } ], "vout": [ { "amount": 489606941801, "target": { "key": "81b31f46449e4021f17399d8eb191cadc78314198126b69275c40554f3f22af6" } } ], "extra": [ 1, 87, 194, 13, 160, 59, 207, 229, 223, 236, 31, 114, 108, 35, 249, 123, 30, 32, 2, 227, 10, 46, 100, 163, 36, 141, 107, 250, 205, 59, 46, 201, 145, 2, 17, 0, 0, 0, 18, 138, 46, 224, 217, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8