Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67d52ea5b33331dc3c82a1d63671feb64e78517824321b71aae17153e9abe83f

Tx prefix hash: 548a611f5b4e94c5e78ac4fd767dd7ac6dfcb2899926bd4fd32f4355e754be74
Tx public key: 9e428ac5a0c56a34dd15c2c5934b6b6965df6bbec39bfac835ab8f84e7f2605d
Timestamp: 1707013079 Timestamp [UCT]: 2024-02-04 02:17:59 Age [y:d:h:m:s]: 00:346:20:18:35
Block: 949876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248303 RingCT/type: yes/0
Extra: 019e428ac5a0c56a34dd15c2c5934b6b6965df6bbec39bfac835ab8f84e7f2605d02110000000181d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a40f0566ead0163c3abceac84ee2faf2e877515af8895725034d3678e367d29 0.600000000000 1408410 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": 949886, "vin": [ { "gen": { "height": 949876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a40f0566ead0163c3abceac84ee2faf2e877515af8895725034d3678e367d29" } } ], "extra": [ 1, 158, 66, 138, 197, 160, 197, 106, 52, 221, 21, 194, 197, 147, 75, 107, 105, 101, 223, 107, 190, 195, 155, 250, 200, 53, 171, 143, 132, 231, 242, 96, 93, 2, 17, 0, 0, 0, 1, 129, 215, 29, 85, 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