Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98d38db9fad6f0434cb09fa4d4714746287c10e8cb6ec06077c62686a0e3562a

Tx prefix hash: ddffeff1b9901b3b1bc24ec3fd77b8dd411f872ed0ee5843ad8cdfe85910a88f
Tx public key: 17fb3bb644526c7c9bee7e04ef42778e493da3d752dc81ebe36492dfc6e20c67
Timestamp: 1708465963 Timestamp [UCT]: 2024-02-20 21:52:43 Age [y:d:h:m:s]: 01:115:20:52:31
Block: 961934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343781 RingCT/type: yes/0
Extra: 0117fb3bb644526c7c9bee7e04ef42778e493da3d752dc81ebe36492dfc6e20c670211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 367e7bbcb11e19cecc41bbdcef3a4f8fdfcd8728048f32c39c454134a2db4703 0.600000000000 1421551 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": 961944, "vin": [ { "gen": { "height": 961934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "367e7bbcb11e19cecc41bbdcef3a4f8fdfcd8728048f32c39c454134a2db4703" } } ], "extra": [ 1, 23, 251, 59, 182, 68, 82, 108, 124, 155, 238, 126, 4, 239, 66, 119, 142, 73, 61, 163, 215, 82, 220, 129, 235, 227, 100, 146, 223, 198, 226, 12, 103, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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