Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57f687b40ab717ae7c077b6acaec96632789e05312b3eaac3957c80197f1571f

Tx prefix hash: c10a3a04e24499cf8f58e709b44aea79f0ff7ddcd3ba15d03afdf523d71d5c73
Tx public key: edfec83d402ec7afba08c2fcc703ce77ec1504d5b481dfbf42997f9f1ce7ff2b
Timestamp: 1717015791 Timestamp [UCT]: 2024-05-29 20:49:51 Age [y:d:h:m:s]: 00:300:16:52:01
Block: 1032818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214900 RingCT/type: yes/0
Extra: 01edfec83d402ec7afba08c2fcc703ce77ec1504d5b481dfbf42997f9f1ce7ff2b0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 393d7898d126e4049983bead87aa68e69aafcb69067138d1b199b1a5951e6031 0.600000000000 1501273 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": 1032828, "vin": [ { "gen": { "height": 1032818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "393d7898d126e4049983bead87aa68e69aafcb69067138d1b199b1a5951e6031" } } ], "extra": [ 1, 237, 254, 200, 61, 64, 46, 199, 175, 186, 8, 194, 252, 199, 3, 206, 119, 236, 21, 4, 213, 180, 129, 223, 191, 66, 153, 127, 159, 28, 231, 255, 43, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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