Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b3f625591718cf88cc4bf82295e1ad733602f2b59cd2a9495c9071d8c8a9957

Tx prefix hash: 7ab8a67f84dad81c73dba40aeb275057d010a8e6bfb892d51353c4e4c7e26921
Tx public key: a9037155c958498b2a2bc4ef437fd1234f5da9dadb170f98b253e8a17d6e26d5
Timestamp: 1736886617 Timestamp [UCT]: 2025-01-14 20:30:17 Age [y:d:h:m:s]: 00:154:22:06:26
Block: 1197411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110416 RingCT/type: yes/0
Extra: 01a9037155c958498b2a2bc4ef437fd1234f5da9dadb170f98b253e8a17d6e26d50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee90806de41c198b5b5a7e35547b9c9d69441ecd172a0a056aa1fe63fceadaac 0.600000000000 1684018 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": 1197421, "vin": [ { "gen": { "height": 1197411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee90806de41c198b5b5a7e35547b9c9d69441ecd172a0a056aa1fe63fceadaac" } } ], "extra": [ 1, 169, 3, 113, 85, 201, 88, 73, 139, 42, 43, 196, 239, 67, 127, 209, 35, 79, 93, 169, 218, 219, 23, 15, 152, 178, 83, 232, 161, 125, 110, 38, 213, 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