Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73aed0f458cb1a02d3ffb7781b01aaf24dd60cf6f4ef39d8113bd03775cfbbca

Tx prefix hash: 5d76316a2e4c9f4838832c8edb40d2dc54634ed9eeafe8b157043cf5f3cb4e80
Tx public key: 7fd717dcaad7e41a51085ef8cecc25330950a2993208f6660c0cfb5950f5871c
Timestamp: 1730946423 Timestamp [UCT]: 2024-11-07 02:27:03 Age [y:d:h:m:s]: 00:132:12:45:25
Block: 1148220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94561 RingCT/type: yes/0
Extra: 017fd717dcaad7e41a51085ef8cecc25330950a2993208f6660c0cfb5950f5871c02110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d6b1574f00574a636c80d3a6ebd3bd2dcc0c43a5416408b2785be7fed40fcb6 0.600000000000 1633015 of 15

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": 1148230, "vin": [ { "gen": { "height": 1148220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d6b1574f00574a636c80d3a6ebd3bd2dcc0c43a5416408b2785be7fed40fcb6" } } ], "extra": [ 1, 127, 215, 23, 220, 170, 215, 228, 26, 81, 8, 94, 248, 206, 204, 37, 51, 9, 80, 162, 153, 50, 8, 246, 102, 12, 12, 251, 89, 80, 245, 135, 28, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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