Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31ed7feb8e57df18b1b015f2cf03b129485e7ac8af0df713bd0b9d4c0f13fd45

Tx prefix hash: 38ea5c2e5abead0e2d2d41f0a76f633601a86e9b3f452855c9ce2580a693cf98
Tx public key: 794e96fb8091629e0362061d38396cebf82e5035c791df4f5dfb6a12a9ee8415
Timestamp: 1726003442 Timestamp [UCT]: 2024-09-10 21:24:02 Age [y:d:h:m:s]: 00:118:14:06:40
Block: 1107334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84794 RingCT/type: yes/0
Extra: 01794e96fb8091629e0362061d38396cebf82e5035c791df4f5dfb6a12a9ee841502110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 237b1f6d19ab56fc06a76b3a96413f55036c31681d2ade959cfd86cba9f3c639 0.600000000000 1584945 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": 1107344, "vin": [ { "gen": { "height": 1107334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "237b1f6d19ab56fc06a76b3a96413f55036c31681d2ade959cfd86cba9f3c639" } } ], "extra": [ 1, 121, 78, 150, 251, 128, 145, 98, 158, 3, 98, 6, 29, 56, 57, 108, 235, 248, 46, 80, 53, 199, 145, 223, 79, 93, 251, 106, 18, 169, 238, 132, 21, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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