Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9409e73da6557094843fe88e5fa6c3e7fd90a1303c17eb68c7391b79f8afacf0

Tx prefix hash: df7fef1084d34cd628104c60b5b9642ef634496236c3fbffcd9ab664227c8c59
Tx public key: 949976dc4ac7c99ea5c75633841fa3359379f9b7aa9be5cb79ba2b6d766aa73d
Timestamp: 1731359375 Timestamp [UCT]: 2024-11-11 21:09:35 Age [y:d:h:m:s]: 00:353:04:14:04
Block: 1151638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249968 RingCT/type: yes/0
Extra: 01949976dc4ac7c99ea5c75633841fa3359379f9b7aa9be5cb79ba2b6d766aa73d0211000000068368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa2e3b33a103af8efc543baaf4b08040154596a1fbf4debfe260a5df60df2ced 0.600000000000 1637207 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": 1151648, "vin": [ { "gen": { "height": 1151638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa2e3b33a103af8efc543baaf4b08040154596a1fbf4debfe260a5df60df2ced" } } ], "extra": [ 1, 148, 153, 118, 220, 74, 199, 201, 158, 165, 199, 86, 51, 132, 31, 163, 53, 147, 121, 249, 183, 170, 155, 229, 203, 121, 186, 43, 109, 118, 106, 167, 61, 2, 17, 0, 0, 0, 6, 131, 104, 38, 109, 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