Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b275d075593d969e05d567fa2b33b762c5e4751d3de5f881f714b71c6ccd1040

Tx prefix hash: 737edce4c991c15494dc220e2c5d4b32cd9ad6f2da88da605968b565d9aaa70b
Tx public key: f247c5cb00ba29731f0ef14d4ea04ff8ad3f9e0096f6d0d3bfc0175d42a776c4
Timestamp: 1702361138 Timestamp [UCT]: 2023-12-12 06:05:38 Age [y:d:h:m:s]: 01:093:09:47:54
Block: 911320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327910 RingCT/type: yes/0
Extra: 01f247c5cb00ba29731f0ef14d4ea04ff8ad3f9e0096f6d0d3bfc0175d42a776c402110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfddfc13a0517ed5b17b279b9feff8e0db2e616d3cab004c891929f8c3dcd7f4 0.600000000000 1368501 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": 911330, "vin": [ { "gen": { "height": 911320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfddfc13a0517ed5b17b279b9feff8e0db2e616d3cab004c891929f8c3dcd7f4" } } ], "extra": [ 1, 242, 71, 197, 203, 0, 186, 41, 115, 31, 14, 241, 77, 78, 160, 79, 248, 173, 63, 158, 0, 150, 246, 208, 211, 191, 192, 23, 93, 66, 167, 118, 196, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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