Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb3840c5a8da4a3219117127a4ed876ec09e6ef6a074ce046db0b8fc9ad202e5

Tx prefix hash: 2835201dad3972d65a0db9584a60a183a487ab8865e97c1e72f4980080959ef2
Tx public key: 0ac1ceea879912d5b55a7829ae62f21e6fef5f482111e6208dd23e6f8f9e1203
Timestamp: 1741144931 Timestamp [UCT]: 2025-03-05 03:22:11 Age [y:d:h:m:s]: 00:066:14:53:47
Block: 1232400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47644 RingCT/type: yes/0
Extra: 010ac1ceea879912d5b55a7829ae62f21e6fef5f482111e6208dd23e6f8f9e12030211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b678a9bb7391841b413a797d4e183d82fc9a99be6299d4fee450103f1180225d 0.600000000000 1719313 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": 1232410, "vin": [ { "gen": { "height": 1232400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b678a9bb7391841b413a797d4e183d82fc9a99be6299d4fee450103f1180225d" } } ], "extra": [ 1, 10, 193, 206, 234, 135, 153, 18, 213, 181, 90, 120, 41, 174, 98, 242, 30, 111, 239, 95, 72, 33, 17, 230, 32, 141, 210, 62, 111, 143, 158, 18, 3, 2, 17, 0, 0, 0, 4, 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