Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6f60b2b5f77a7e9d557a8d8294fb4a0ae15b0bdc04a9ec7030f25693b50f881

Tx prefix hash: 6f868c55b57986034b45780dd3631018870ac43d0e6c05717b53f11ae0cfab78
Tx public key: d72490ca4a5d1e1e19a0da832fa8d17113473ca9da4a60001e26c137fd11b822
Timestamp: 1706626119 Timestamp [UCT]: 2024-01-30 14:48:39 Age [y:d:h:m:s]: 01:294:11:57:36
Block: 946659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469289 RingCT/type: yes/0
Extra: 01d72490ca4a5d1e1e19a0da832fa8d17113473ca9da4a60001e26c137fd11b82202110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08f262786700d0d711ada200652eb8b12fd68586fc732327db4d49a6eecd3777 0.600000000000 1404993 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": 946669, "vin": [ { "gen": { "height": 946659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08f262786700d0d711ada200652eb8b12fd68586fc732327db4d49a6eecd3777" } } ], "extra": [ 1, 215, 36, 144, 202, 74, 93, 30, 30, 25, 160, 218, 131, 47, 168, 209, 113, 19, 71, 60, 169, 218, 74, 96, 0, 30, 38, 193, 55, 253, 17, 184, 34, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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