Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 803f92b3eafa21e1436b9487cebbd21d1a93ce485524c80696216927842e0e0d

Tx prefix hash: c24db1667c7be98032de0d378eb807d6ba1361b7b196a2510bc2e58bd27e9555
Tx public key: 84c6a5a2c4d2404629a32bad22088d32c96caf9bf52ce0c835cd77b6c0db9c51
Timestamp: 1708726576 Timestamp [UCT]: 2024-02-23 22:16:16 Age [y:d:h:m:s]: 01:054:16:41:36
Block: 964094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300124 RingCT/type: yes/0
Extra: 0184c6a5a2c4d2404629a32bad22088d32c96caf9bf52ce0c835cd77b6c0db9c5102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5dcb1edd138dbcfee5da5c4d945fea46e8abcce4c8f101723d87a8c534a3235 0.600000000000 1423821 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": 964104, "vin": [ { "gen": { "height": 964094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5dcb1edd138dbcfee5da5c4d945fea46e8abcce4c8f101723d87a8c534a3235" } } ], "extra": [ 1, 132, 198, 165, 162, 196, 210, 64, 70, 41, 163, 43, 173, 34, 8, 141, 50, 201, 108, 175, 155, 245, 44, 224, 200, 53, 205, 119, 182, 192, 219, 156, 81, 2, 17, 0, 0, 0, 2, 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