Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf50fff3389807dd569a3e7724a21a2e5084fac1c82466d5a7b71b82adc1f980

Tx prefix hash: 0271e5473d5d21c846507d124f39d44f81bfc9638dc51a1793c11ce3779c2be6
Tx public key: ebe9349e7b2fa70543d578f48c6adf163e281fe1ecdf27d84ff5a2c765a223d1
Timestamp: 1720618593 Timestamp [UCT]: 2024-07-10 13:36:33 Age [y:d:h:m:s]: 00:310:12:46:59
Block: 1062684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221898 RingCT/type: yes/0
Extra: 01ebe9349e7b2fa70543d578f48c6adf163e281fe1ecdf27d84ff5a2c765a223d102110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e785a861cc7c3aff57603868ae6a42c73c7408a7331cc68cfeece78c65d9ff8 0.600000000000 1533191 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": 1062694, "vin": [ { "gen": { "height": 1062684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e785a861cc7c3aff57603868ae6a42c73c7408a7331cc68cfeece78c65d9ff8" } } ], "extra": [ 1, 235, 233, 52, 158, 123, 47, 167, 5, 67, 213, 120, 244, 140, 106, 223, 22, 62, 40, 31, 225, 236, 223, 39, 216, 79, 245, 162, 199, 101, 162, 35, 209, 2, 17, 0, 0, 0, 9, 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