Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6453502793ccccec990171886e810bf58a1e208951c2932e3a13cdcd7533a5bf

Tx prefix hash: 132883e212c9cfa91f44b37274bb0adab594817a16d910deefe65d08e1d3720f
Tx public key: 61941eb6bf43a9aa18ef548c29bcac0d913e1d1baa5e2f3d52de8b7f7a3f6c98
Timestamp: 1698075840 Timestamp [UCT]: 2023-10-23 15:44:00 Age [y:d:h:m:s]: 01:091:22:05:32
Block: 875993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326903 RingCT/type: yes/0
Extra: 0161941eb6bf43a9aa18ef548c29bcac0d913e1d1baa5e2f3d52de8b7f7a3f6c9802110000000575e3f0e9000000000000000000

1 output(s) for total of 0.768195162000 dcy

stealth address amount amount idx
00: 2dfc5894ce193dd4c1bda1af3bed66f936b1812f582a3d9a12b00db27d30e674 0.768195162000 1331299 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": 876003, "vin": [ { "gen": { "height": 875993 } } ], "vout": [ { "amount": 768195162, "target": { "key": "2dfc5894ce193dd4c1bda1af3bed66f936b1812f582a3d9a12b00db27d30e674" } } ], "extra": [ 1, 97, 148, 30, 182, 191, 67, 169, 170, 24, 239, 84, 140, 41, 188, 172, 13, 145, 62, 29, 27, 170, 94, 47, 61, 82, 222, 139, 127, 122, 63, 108, 152, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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