Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6ff75484215cb0eb914d0080dd206098904d7368ba6bcba5efce6f274e7f913

Tx prefix hash: 2f4ed146cf4a2e8cc1c43dd9932dc5136aa39eba9391d8cd8b896cfa46c2e968
Tx public key: b571817a09273405de4a1cb6230b7979efe93c7440a3349033529f5d4374ce77
Timestamp: 1725687428 Timestamp [UCT]: 2024-09-07 05:37:08 Age [y:d:h:m:s]: 00:122:04:32:35
Block: 1104709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87386 RingCT/type: yes/0
Extra: 01b571817a09273405de4a1cb6230b7979efe93c7440a3349033529f5d4374ce7702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 617757fa7cc28c7ac2585189c7c50f5f3d832f1a46ca01355c098d9aaf8c7cba 0.600000000000 1581954 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": 1104719, "vin": [ { "gen": { "height": 1104709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "617757fa7cc28c7ac2585189c7c50f5f3d832f1a46ca01355c098d9aaf8c7cba" } } ], "extra": [ 1, 181, 113, 129, 122, 9, 39, 52, 5, 222, 74, 28, 182, 35, 11, 121, 121, 239, 233, 60, 116, 64, 163, 52, 144, 51, 82, 159, 93, 67, 116, 206, 119, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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