Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96377abe8241db03854d44170986d9219809c2fc60b2bdb9e81c0eeb90f14aab

Tx prefix hash: df921a0c2eead7e62765c8808cbf171bdd1f1963cd57934a76e123e444919c6b
Tx public key: 81aea9fd5520c5c9b96de53158d3104eaadf29ea9597b76940e19b6d2ea42355
Timestamp: 1701261730 Timestamp [UCT]: 2023-11-29 12:42:10 Age [y:d:h:m:s]: 01:126:13:30:32
Block: 902210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351598 RingCT/type: yes/0
Extra: 0181aea9fd5520c5c9b96de53158d3104eaadf29ea9597b76940e19b6d2ea4235502110000000275e3f0e9000000000000000000

1 output(s) for total of 0.628932047000 dcy

stealth address amount amount idx
00: 67ee345aa610a1616288933db9b23e24cc586a81a39d1986629fda2b6291e3d6 0.628932047000 1358829 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": 902220, "vin": [ { "gen": { "height": 902210 } } ], "vout": [ { "amount": 628932047, "target": { "key": "67ee345aa610a1616288933db9b23e24cc586a81a39d1986629fda2b6291e3d6" } } ], "extra": [ 1, 129, 174, 169, 253, 85, 32, 197, 201, 185, 109, 229, 49, 88, 211, 16, 78, 170, 223, 41, 234, 149, 151, 183, 105, 64, 225, 155, 109, 46, 164, 35, 85, 2, 17, 0, 0, 0, 2, 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