Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d89354152ee3c6911904ead0c0e3dad660e950df2208aa9465c7402f71780f88

Tx prefix hash: 0e729c76d627c607e15e8f8d47939c43ee100445d2f80f3d015ad2895f953458
Tx public key: 3b2add42f31b643f11491ee17d2d2c5c4aae19973349648815b05af23486d0ce
Timestamp: 1714252806 Timestamp [UCT]: 2024-04-27 21:20:06 Age [y:d:h:m:s]: 01:209:07:47:20
Block: 1009904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408264 RingCT/type: yes/0
Extra: 013b2add42f31b643f11491ee17d2d2c5c4aae19973349648815b05af23486d0ce0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0cf9152f34faff8c7eb7d2f46efd9198aa3174a6f35a9d7bf7ed5f461eb553a 0.600000000000 1471706 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": 1009914, "vin": [ { "gen": { "height": 1009904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0cf9152f34faff8c7eb7d2f46efd9198aa3174a6f35a9d7bf7ed5f461eb553a" } } ], "extra": [ 1, 59, 42, 221, 66, 243, 27, 100, 63, 17, 73, 30, 225, 125, 45, 44, 92, 74, 174, 25, 151, 51, 73, 100, 136, 21, 176, 90, 242, 52, 134, 208, 206, 2, 17, 0, 0, 0, 7, 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