Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3de9248071773d3e87524dd0bba6066f47b53eabd1fa5f17a93906682fc1812

Tx prefix hash: bdfe6f2da2db7835343ffa5163478bcffb2f918003acfd01f2354e6c43b26477
Tx public key: 0f62e5fd9c375d9dca6552df9e20939d1376ba9ed65b6be151c60138689943e5
Timestamp: 1697995947 Timestamp [UCT]: 2023-10-22 17:32:27 Age [y:d:h:m:s]: 01:161:15:47:32
Block: 875329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376547 RingCT/type: yes/0
Extra: 010f62e5fd9c375d9dca6552df9e20939d1376ba9ed65b6be151c60138689943e502110000000233af99f4000000000000000000

1 output(s) for total of 0.772096664000 dcy

stealth address amount amount idx
00: cc36d1de0a459c0e4cc0893766b3ec0b428c848e9896acf0f5a0cbc651b1c55f 0.772096664000 1330581 of 0

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": 875339, "vin": [ { "gen": { "height": 875329 } } ], "vout": [ { "amount": 772096664, "target": { "key": "cc36d1de0a459c0e4cc0893766b3ec0b428c848e9896acf0f5a0cbc651b1c55f" } } ], "extra": [ 1, 15, 98, 229, 253, 156, 55, 93, 157, 202, 101, 82, 223, 158, 32, 147, 157, 19, 118, 186, 158, 214, 91, 107, 225, 81, 198, 1, 56, 104, 153, 67, 229, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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