Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4c08a55d0c4fb69784a564fd7757284ab45ea536180ffe7e294e836eb314bd2

Tx prefix hash: 95162f7c375edcbe8a650f1e574647a22a954059e23e543c9b29867133d83c3d
Tx public key: c9fe454d02796ae91dc915b26e9d7fd2709d4d188f1337ab6c9b26a4e5c99210
Timestamp: 1736060351 Timestamp [UCT]: 2025-01-05 06:59:11 Age [y:d:h:m:s]: 00:169:05:11:21
Block: 1190579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120558 RingCT/type: yes/0
Extra: 01c9fe454d02796ae91dc915b26e9d7fd2709d4d188f1337ab6c9b26a4e5c992100211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee88fd583cc3ebddfacd21f60cbe550057e4e77f190d19de43daf64352b74516 0.600000000000 1677096 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": 1190589, "vin": [ { "gen": { "height": 1190579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee88fd583cc3ebddfacd21f60cbe550057e4e77f190d19de43daf64352b74516" } } ], "extra": [ 1, 201, 254, 69, 77, 2, 121, 106, 233, 29, 201, 21, 178, 110, 157, 127, 210, 112, 157, 77, 24, 143, 19, 55, 171, 108, 155, 38, 164, 229, 201, 146, 16, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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