Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0330727e33879bb1bdf894055cdb5126ed6f1ab58289aee1d5c9c63d863b5125

Tx prefix hash: 0e5faf1fa5e41cc623310662f93e7a3bb9bac10425e90b0282464416e03893f9
Tx public key: bf675b0961cebb80d65c26ee8c83018d5fbcda0d0acb4c0b7a5e137c5110a11d
Timestamp: 1727680515 Timestamp [UCT]: 2024-09-30 07:15:15 Age [y:d:h:m:s]: 00:117:13:50:35
Block: 1121232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84021 RingCT/type: yes/0
Extra: 01bf675b0961cebb80d65c26ee8c83018d5fbcda0d0acb4c0b7a5e137c5110a11d02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b312e045fc45fd4e0fcc3527ab434b4201db895ae6cfc6023c855f94b15ceb3 0.600000000000 1603431 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": 1121242, "vin": [ { "gen": { "height": 1121232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b312e045fc45fd4e0fcc3527ab434b4201db895ae6cfc6023c855f94b15ceb3" } } ], "extra": [ 1, 191, 103, 91, 9, 97, 206, 187, 128, 214, 92, 38, 238, 140, 131, 1, 141, 95, 188, 218, 13, 10, 203, 76, 11, 122, 94, 19, 124, 81, 16, 161, 29, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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