Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf964fef9b441d8c1f5bac2f175418cf8f8082247e589744229445e5212b9531

Tx prefix hash: fa03ab725d3dd1419f75b6cfb0bebd9021a342e221ab16f9f6f3e5b78c91682e
Tx public key: 90d5f4047bfc182fbf1fe1b59696999cedd1d5d17d1eb9a87120560e7b659e30
Timestamp: 1732850222 Timestamp [UCT]: 2024-11-29 03:17:02 Age [y:d:h:m:s]: 00:128:11:09:45
Block: 1163990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91608 RingCT/type: yes/0
Extra: 0190d5f4047bfc182fbf1fe1b59696999cedd1d5d17d1eb9a87120560e7b659e300211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d025c411858b31fdbe0e927a172721393a4714fb89ec8c4a1a31e04e8dc9e5d0 0.600000000000 1649661 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": 1164000, "vin": [ { "gen": { "height": 1163990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d025c411858b31fdbe0e927a172721393a4714fb89ec8c4a1a31e04e8dc9e5d0" } } ], "extra": [ 1, 144, 213, 244, 4, 123, 252, 24, 47, 191, 31, 225, 181, 150, 150, 153, 156, 237, 209, 213, 209, 125, 30, 185, 168, 113, 32, 86, 14, 123, 101, 158, 48, 2, 17, 0, 0, 0, 1, 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