Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8b84a3bbe264e101da6b1f4e31383dc04d8954e6bea46ef24239dc0b6363f23

Tx prefix hash: f1966b5545b40a93bfe936087e0994a685d148b1aa71a89b1b1a792f143367a2
Tx public key: 7228d1be0ba2624a7b60b3ba539c30edcf9e1f794f746f2ae9be5549c0aa7137
Timestamp: 1726562237 Timestamp [UCT]: 2024-09-17 08:37:17 Age [y:d:h:m:s]: 00:237:18:33:17
Block: 1111956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169787 RingCT/type: yes/0
Extra: 017228d1be0ba2624a7b60b3ba539c30edcf9e1f794f746f2ae9be5549c0aa713702110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd3535d5f581d016e6a64da41454366dc91faf2c0be1a80361da8696857601b8 0.600000000000 1591101 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": 1111966, "vin": [ { "gen": { "height": 1111956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd3535d5f581d016e6a64da41454366dc91faf2c0be1a80361da8696857601b8" } } ], "extra": [ 1, 114, 40, 209, 190, 11, 162, 98, 74, 123, 96, 179, 186, 83, 156, 48, 237, 207, 158, 31, 121, 79, 116, 111, 42, 233, 190, 85, 73, 192, 170, 113, 55, 2, 17, 0, 0, 0, 7, 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