Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fc1e4df31cd8ac12dc5da92e24f28012ed011a8cf67b305105f030b6cc027dc

Tx prefix hash: e8dfcf644ac2da30d2a3d7fe438dd021b2f939ab12939656f082cdc40247cb6e
Tx public key: 045ec8337aed6356d91fc1f84439b8efc6e178633d79a39abc3c2c23e066b23e
Timestamp: 1720969393 Timestamp [UCT]: 2024-07-14 15:03:13 Age [y:d:h:m:s]: 00:274:18:50:54
Block: 1065596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196322 RingCT/type: yes/0
Extra: 01045ec8337aed6356d91fc1f84439b8efc6e178633d79a39abc3c2c23e066b23e02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f138dd96a189467e5da44fbc7d1b0af1a0dfb38638597a9730802e0937c4c44 0.600000000000 1536145 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": 1065606, "vin": [ { "gen": { "height": 1065596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f138dd96a189467e5da44fbc7d1b0af1a0dfb38638597a9730802e0937c4c44" } } ], "extra": [ 1, 4, 94, 200, 51, 122, 237, 99, 86, 217, 31, 193, 248, 68, 57, 184, 239, 198, 225, 120, 99, 61, 121, 163, 154, 188, 60, 44, 35, 224, 102, 178, 62, 2, 17, 0, 0, 0, 5, 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