Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 597db0c63bc2f532e2ff1085e6b673081581126cdaf5c57eb45619c1ed8d9ccc

Tx prefix hash: 2fb71e0c31dac6b14d10e1f7fece0c619f5e010f169817b40d94338cbcdc02fb
Tx public key: 7ce8c6302e3e9e1d3e53cf62df78a2f03761cfd9df5cf9c52f96434f379e042a
Timestamp: 1733830820 Timestamp [UCT]: 2024-12-10 11:40:20 Age [y:d:h:m:s]: 00:104:22:20:17
Block: 1172127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74768 RingCT/type: yes/0
Extra: 017ce8c6302e3e9e1d3e53cf62df78a2f03761cfd9df5cf9c52f96434f379e042a0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 159fd72d65c7ea23077fb4b0134d8448299a0fee07440dcfd5739e51bbf1f892 0.600000000000 1657978 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": 1172137, "vin": [ { "gen": { "height": 1172127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "159fd72d65c7ea23077fb4b0134d8448299a0fee07440dcfd5739e51bbf1f892" } } ], "extra": [ 1, 124, 232, 198, 48, 46, 62, 158, 29, 62, 83, 207, 98, 223, 120, 162, 240, 55, 97, 207, 217, 223, 92, 249, 197, 47, 150, 67, 79, 55, 158, 4, 42, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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