Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08c367ad3892f4734df10e808198f69953fb9cbe51da9a7c66d24ba04d3f10c1

Tx prefix hash: 8fd93d2c4ff08d911407947c5b8103ddfb44c43029f6023084c1ca31b17044e2
Tx public key: 3010ba5cf9fb87cce9bd4468cf79e96ab3be85402c162bbbb0f74ec405a9ecb9
Timestamp: 1739771772 Timestamp [UCT]: 2025-02-17 05:56:12 Age [y:d:h:m:s]: 00:024:18:56:23
Block: 1221002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17774 RingCT/type: yes/0
Extra: 013010ba5cf9fb87cce9bd4468cf79e96ab3be85402c162bbbb0f74ec405a9ecb90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a8487f2e6f01c236700d2df0ff3d379697fb095758fefbd1fa724f4dc4009b2 0.600000000000 1707845 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": 1221012, "vin": [ { "gen": { "height": 1221002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a8487f2e6f01c236700d2df0ff3d379697fb095758fefbd1fa724f4dc4009b2" } } ], "extra": [ 1, 48, 16, 186, 92, 249, 251, 135, 204, 233, 189, 68, 104, 207, 121, 233, 106, 179, 190, 133, 64, 44, 22, 43, 187, 176, 247, 78, 196, 5, 169, 236, 185, 2, 17, 0, 0, 0, 2, 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