Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cf6ca9c7feab9e5ad04e76a65673f5a0e0a7c5a98321beb0667f8222afb451e

Tx prefix hash: 1ab69e98723177866f5ef57febf82a48dd5c6dc22fbe1c131674acd318431488
Tx public key: a3b81f518bb73323e40219403abe9676f341987d702b32fb9c6c34137815b8e1
Timestamp: 1724717699 Timestamp [UCT]: 2024-08-27 00:14:59 Age [y:d:h:m:s]: 00:058:02:10:11
Block: 1096660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41582 RingCT/type: yes/0
Extra: 01a3b81f518bb73323e40219403abe9676f341987d702b32fb9c6c34137815b8e102110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06dd3ff3be6d0fa1c849f2c2bf96e397f66bc9725c8203eae8a417d57a057ddd 0.600000000000 1571853 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": 1096670, "vin": [ { "gen": { "height": 1096660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06dd3ff3be6d0fa1c849f2c2bf96e397f66bc9725c8203eae8a417d57a057ddd" } } ], "extra": [ 1, 163, 184, 31, 81, 139, 183, 51, 35, 228, 2, 25, 64, 58, 190, 150, 118, 243, 65, 152, 125, 112, 43, 50, 251, 156, 108, 52, 19, 120, 21, 184, 225, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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