Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 333552d1e669fc6346f874f256f575cf99ee8241a7af853e21f913f1c8d6d869

Tx prefix hash: eea33e001bf0638037ad541c523e33b48658486e921ac4387b50aaac68d34d4e
Tx public key: 0314e43250c938600c18db4713e1dd4b5ccd21238e845d2937f5c09da531c003
Timestamp: 1712303429 Timestamp [UCT]: 2024-04-05 07:50:29 Age [y:d:h:m:s]: 01:067:12:57:40
Block: 993720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309278 RingCT/type: yes/0
Extra: 010314e43250c938600c18db4713e1dd4b5ccd21238e845d2937f5c09da531c00302110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e008f68b4bd4b0f197ee703a2d928aa4cd5c53edfb326caf819f9394281430d6 0.600000000000 1454108 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": 993730, "vin": [ { "gen": { "height": 993720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e008f68b4bd4b0f197ee703a2d928aa4cd5c53edfb326caf819f9394281430d6" } } ], "extra": [ 1, 3, 20, 228, 50, 80, 201, 56, 96, 12, 24, 219, 71, 19, 225, 221, 75, 92, 205, 33, 35, 142, 132, 93, 41, 55, 245, 192, 157, 165, 49, 192, 3, 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