Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 931a48a2a7d2997a2bb2032c1acf5a7eeadba2020166e3a37f11044b6538657b

Tx prefix hash: e165196568cb1a13c1bde1b205e62cb148ee765ea14baec617066bcae97a4db3
Tx public key: 056971ac5c5aa66e315a515fe96d53d256fb0bdb051376ee434a18f35f343bc9
Timestamp: 1737509150 Timestamp [UCT]: 2025-01-22 01:25:50 Age [y:d:h:m:s]: 00:149:12:32:31
Block: 1202521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106575 RingCT/type: yes/0
Extra: 01056971ac5c5aa66e315a515fe96d53d256fb0bdb051376ee434a18f35f343bc90211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3fe961ab8c8d430c91a523c2c3424c66c82dd453a9a630b4886bb1633e4010f 0.600000000000 1689186 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": 1202531, "vin": [ { "gen": { "height": 1202521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3fe961ab8c8d430c91a523c2c3424c66c82dd453a9a630b4886bb1633e4010f" } } ], "extra": [ 1, 5, 105, 113, 172, 92, 90, 166, 110, 49, 90, 81, 95, 233, 109, 83, 210, 86, 251, 11, 219, 5, 19, 118, 238, 67, 74, 24, 243, 95, 52, 59, 201, 2, 17, 0, 0, 0, 5, 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