Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fbdc2c055e7219a7bf462001324639cf2535e144c8fcd9a7a12fdb6dacbb5a2

Tx prefix hash: 9460d336781208e92849210aecfeca86837a5aebea38a1fdb1906f6a5a3c8692
Tx public key: c7dc1b89f9e8b8e49b87b2e83eb3739299b35d459258c32ef4e1850dbdc87fa4
Timestamp: 1711702878 Timestamp [UCT]: 2024-03-29 09:01:18 Age [y:d:h:m:s]: 01:071:07:58:29
Block: 988781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311984 RingCT/type: yes/0
Extra: 01c7dc1b89f9e8b8e49b87b2e83eb3739299b35d459258c32ef4e1850dbdc87fa40211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2064d8fbd92bdabdf4fda571a393c78dfd82b0678f5c2675bccd45753198c42d 0.600000000000 1449066 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": 988791, "vin": [ { "gen": { "height": 988781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2064d8fbd92bdabdf4fda571a393c78dfd82b0678f5c2675bccd45753198c42d" } } ], "extra": [ 1, 199, 220, 27, 137, 249, 232, 184, 228, 155, 135, 178, 232, 62, 179, 115, 146, 153, 179, 93, 69, 146, 88, 195, 46, 244, 225, 133, 13, 189, 200, 127, 164, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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