Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41e5e6b47e5bfa288a2e475f89ec7efc27ac6395b0939975dd4ef0b77a0b4ff6

Tx prefix hash: c72b4abaefd9362172c3fd42dc0082795614962966fb5b14b3f8d9a01117efcf
Tx public key: 081727db593edbd4ebe963eb259b11cc0157f1eec906d82b8ae3ae75731d19d6
Timestamp: 1724338905 Timestamp [UCT]: 2024-08-22 15:01:45 Age [y:d:h:m:s]: 01:080:11:33:40
Block: 1093541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315964 RingCT/type: yes/0
Extra: 01081727db593edbd4ebe963eb259b11cc0157f1eec906d82b8ae3ae75731d19d602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3bb1a7e213cd0fac26f624e294ad737fdb1fc495279c5d0fa92546e79393239 0.600000000000 1568506 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": 1093551, "vin": [ { "gen": { "height": 1093541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3bb1a7e213cd0fac26f624e294ad737fdb1fc495279c5d0fa92546e79393239" } } ], "extra": [ 1, 8, 23, 39, 219, 89, 62, 219, 212, 235, 233, 99, 235, 37, 155, 17, 204, 1, 87, 241, 238, 201, 6, 216, 43, 138, 227, 174, 117, 115, 29, 25, 214, 2, 17, 0, 0, 0, 1, 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