Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45b583bb3d837cc49f4bea0fee31224437d259b1fbe01a8fdcffbc9aab5111c6

Tx prefix hash: 41539057a019130dea50be1193c1ae8f0ef5910c7c48215047f519a005b2d737
Tx public key: 49d32b51d2f4fdd41289d4c179c063de281eb8d105084ee123b988da7583c2c7
Timestamp: 1648241081 Timestamp [UCT]: 2022-03-25 20:44:41 Age [y:d:h:m:s]: 03:220:12:34:34
Block: 466337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 935506 RingCT/type: yes/0
Extra: 0149d32b51d2f4fdd41289d4c179c063de281eb8d105084ee123b988da7583c2c702110000000f37cb3088000000000000000000

1 output(s) for total of 17.491706766000 dcy

stealth address amount amount idx
00: 7e177c0d2ae4f468451dc44f9bbfd638c15c5838b9cde03104a206e17eca1089 17.491706766000 884636 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": 466347, "vin": [ { "gen": { "height": 466337 } } ], "vout": [ { "amount": 17491706766, "target": { "key": "7e177c0d2ae4f468451dc44f9bbfd638c15c5838b9cde03104a206e17eca1089" } } ], "extra": [ 1, 73, 211, 43, 81, 210, 244, 253, 212, 18, 137, 212, 193, 121, 192, 99, 222, 40, 30, 184, 209, 5, 8, 78, 225, 35, 185, 136, 218, 117, 131, 194, 199, 2, 17, 0, 0, 0, 15, 55, 203, 48, 136, 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