Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87a02284d075fc9623a253b96ffe4e0d51d296b11d7275e940a6e7d8502816dc

Tx prefix hash: 13173364b727afcdf7913c8d61ac66ec7e45bf17de42d824cf591724d0c3021a
Tx public key: ebcc8579182910b3815d0633d7b2b193c2a8c62b4969c273dd8ceda0384b6952
Timestamp: 1738333356 Timestamp [UCT]: 2025-01-31 14:22:36 Age [y:d:h:m:s]: 01:000:21:33:21
Block: 1209124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259183 RingCT/type: yes/0
Extra: 01ebcc8579182910b3815d0633d7b2b193c2a8c62b4969c273dd8ceda0384b69520211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d517b549188a9a0a8789028d9ea2865c860c36addd4df9a9533133002a7d0de8 0.600000000000 1695865 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": 1209134, "vin": [ { "gen": { "height": 1209124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d517b549188a9a0a8789028d9ea2865c860c36addd4df9a9533133002a7d0de8" } } ], "extra": [ 1, 235, 204, 133, 121, 24, 41, 16, 179, 129, 93, 6, 51, 215, 178, 177, 147, 194, 168, 198, 43, 73, 105, 194, 115, 221, 140, 237, 160, 56, 75, 105, 82, 2, 17, 0, 0, 0, 6, 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