Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7365a7ed1778c5b90789fbc65bbf7fe44fb0939baef74b8f46eb8d8d7ee02ca2

Tx prefix hash: 4248b44bae47f295efef5f445bb312d219f804f157cf029713ffe0a078e24029
Tx public key: a72b59336e84ea4d3cf47df725f6b5e972ef81c05d57228233049f24146c5dea
Timestamp: 1736108415 Timestamp [UCT]: 2025-01-05 20:20:15 Age [y:d:h:m:s]: 00:106:18:31:11
Block: 1190977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76087 RingCT/type: yes/0
Extra: 01a72b59336e84ea4d3cf47df725f6b5e972ef81c05d57228233049f24146c5dea02110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e9132299ee2b3917422b803e2d64353f8ee8005a7b99fe90ebd1670941ee09d 0.600000000000 1677500 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": 1190987, "vin": [ { "gen": { "height": 1190977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e9132299ee2b3917422b803e2d64353f8ee8005a7b99fe90ebd1670941ee09d" } } ], "extra": [ 1, 167, 43, 89, 51, 110, 132, 234, 77, 60, 244, 125, 247, 37, 246, 181, 233, 114, 239, 129, 192, 93, 87, 34, 130, 51, 4, 159, 36, 20, 108, 93, 234, 2, 17, 0, 0, 0, 15, 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