Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feb894c1e12af17fc05a77af4785c87f6833005700cab3c9f1cbaea367db072a

Tx prefix hash: a0c127221be7c5f992cebab0e2bab9786efe0fc94e18dcb5525c32a835cb5aa1
Tx public key: 28ef1e726354869eef80b8d01b480e1b526663b6f65a38267e5e50997eba1b74
Timestamp: 1711198329 Timestamp [UCT]: 2024-03-23 12:52:09 Age [y:d:h:m:s]: 01:056:05:03:26
Block: 984604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301157 RingCT/type: yes/0
Extra: 0128ef1e726354869eef80b8d01b480e1b526663b6f65a38267e5e50997eba1b7402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c823d0e8c717940746505f7f35ef26a98225ad74781d22db4ad77b6eb6e43c7a 0.600000000000 1444775 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": 984614, "vin": [ { "gen": { "height": 984604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c823d0e8c717940746505f7f35ef26a98225ad74781d22db4ad77b6eb6e43c7a" } } ], "extra": [ 1, 40, 239, 30, 114, 99, 84, 134, 158, 239, 128, 184, 208, 27, 72, 14, 27, 82, 102, 99, 182, 246, 90, 56, 38, 126, 94, 80, 153, 126, 186, 27, 116, 2, 17, 0, 0, 0, 2, 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