Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51ea4a56d3e778e38e020339f8d4afe97c3276cc9306220dfa15d44f343cc8af

Tx prefix hash: ee24efdeb2fc495c30675fef32b371fd7bde3fa6b0872c479c5f4d88ae1f4d78
Tx public key: 2231b15a7e4e920dc70179415a804bb7b3d9aaa6f4418a749ca0c3fde46cf26d
Timestamp: 1716494783 Timestamp [UCT]: 2024-05-23 20:06:23 Age [y:d:h:m:s]: 00:315:10:34:37
Block: 1028504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225447 RingCT/type: yes/0
Extra: 012231b15a7e4e920dc70179415a804bb7b3d9aaa6f4418a749ca0c3fde46cf26d0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 137d1e03accd1f3505c40824d1d1e0f25444f9804d12b03694a085561e368e42 0.600000000000 1496497 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": 1028514, "vin": [ { "gen": { "height": 1028504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "137d1e03accd1f3505c40824d1d1e0f25444f9804d12b03694a085561e368e42" } } ], "extra": [ 1, 34, 49, 177, 90, 126, 78, 146, 13, 199, 1, 121, 65, 90, 128, 75, 183, 179, 217, 170, 166, 244, 65, 138, 116, 156, 160, 195, 253, 228, 108, 242, 109, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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