Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 729df4e69501e7735b1b936653e592f7375e05c8884544b2689213a38219181e

Tx prefix hash: 12768f6d5824d1cef78709f6363c1820dcee27b2d6990522123d745a05c54a01
Tx public key: 9b49641831b4c5b67bfc30ce6efec149837ff42e6ae8ba2a4d57c885f04a2a84
Timestamp: 1710431526 Timestamp [UCT]: 2024-03-14 15:52:06 Age [y:d:h:m:s]: 01:239:20:55:20
Block: 978253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430121 RingCT/type: yes/0
Extra: 019b49641831b4c5b67bfc30ce6efec149837ff42e6ae8ba2a4d57c885f04a2a8402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc617f71be0a40656a4b4b5c106125b03f36d58899d0e2334665a9958d5f8e6d 0.600000000000 1438276 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": 978263, "vin": [ { "gen": { "height": 978253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc617f71be0a40656a4b4b5c106125b03f36d58899d0e2334665a9958d5f8e6d" } } ], "extra": [ 1, 155, 73, 100, 24, 49, 180, 197, 182, 123, 252, 48, 206, 110, 254, 193, 73, 131, 127, 244, 46, 106, 232, 186, 42, 77, 87, 200, 133, 240, 74, 42, 132, 2, 17, 0, 0, 0, 3, 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