Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 728906d7932cf0d9ce394aacb3db54666094cc868d2c63a07061a9f844c4c5e0

Tx prefix hash: 2e7221e7bbb1b4f60b5fcc21ec0e0b5956437e9882d9794a7f65d2785b5bbfd0
Tx public key: 854f01d94d776a0ae425a9952e3b3bc57b74e696e9f8ad3fbdd2ca5997672a42
Timestamp: 1743554631 Timestamp [UCT]: 2025-04-02 00:43:51 Age [y:d:h:m:s]: 00:305:19:26:06
Block: 1252334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216227 RingCT/type: yes/0
Extra: 01854f01d94d776a0ae425a9952e3b3bc57b74e696e9f8ad3fbdd2ca5997672a42021100000005a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4223ee70c0d26cbb47596942eb9588a4c2395d92713eff386a998c3489153de 0.600000000000 1739415 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": 1252344, "vin": [ { "gen": { "height": 1252334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4223ee70c0d26cbb47596942eb9588a4c2395d92713eff386a998c3489153de" } } ], "extra": [ 1, 133, 79, 1, 217, 77, 119, 106, 10, 228, 37, 169, 149, 46, 59, 59, 197, 123, 116, 230, 150, 233, 248, 173, 63, 189, 210, 202, 89, 151, 103, 42, 66, 2, 17, 0, 0, 0, 5, 162, 237, 1, 107, 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