Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ba1ae419f594dd62932f100ca952489188c67a064f255f33e5bbc6fe755ffbb

Tx prefix hash: 53bf59c7b5fee01403691a5c4fd3314a9c6d81c4db07b7738db50a53e4924f17
Tx public key: 0627733779d073cd2d915030476086d0bc4af993e638a0733a48aba5edc5d8cc
Timestamp: 1719387093 Timestamp [UCT]: 2024-06-26 07:31:33 Age [y:d:h:m:s]: 00:305:01:06:47
Block: 1052469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217993 RingCT/type: yes/0
Extra: 010627733779d073cd2d915030476086d0bc4af993e638a0733a48aba5edc5d8cc02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c16f6efd2d3d3bb26b366dfb2c87c14b61aea2c85ff0619e1f0eecd4d577e0e0 0.600000000000 1522796 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": 1052479, "vin": [ { "gen": { "height": 1052469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c16f6efd2d3d3bb26b366dfb2c87c14b61aea2c85ff0619e1f0eecd4d577e0e0" } } ], "extra": [ 1, 6, 39, 115, 55, 121, 208, 115, 205, 45, 145, 80, 48, 71, 96, 134, 208, 188, 74, 249, 147, 230, 56, 160, 115, 58, 72, 171, 165, 237, 197, 216, 204, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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