Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da1698271aed7ff7097cf9cb50291dfbe0796f82d559451ba1905c44e0f15259

Tx prefix hash: f6842a1d6ba6611e90f13e9fb61ced11d565b098bb6e23b17e08d6e45102c926
Tx public key: cfd63fef6892ad905e35674d94daa2564632e3f7fa915a0f893e03f675b57fdc
Timestamp: 1726235123 Timestamp [UCT]: 2024-09-13 13:45:23 Age [y:d:h:m:s]: 00:240:12:10:18
Block: 1109242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171750 RingCT/type: yes/0
Extra: 01cfd63fef6892ad905e35674d94daa2564632e3f7fa915a0f893e03f675b57fdc021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e69bd4d1643a9f2fc014d58feab8d2ad90da30b51e09276934e0300bee1d6116 0.600000000000 1587425 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": 1109252, "vin": [ { "gen": { "height": 1109242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e69bd4d1643a9f2fc014d58feab8d2ad90da30b51e09276934e0300bee1d6116" } } ], "extra": [ 1, 207, 214, 63, 239, 104, 146, 173, 144, 94, 53, 103, 77, 148, 218, 162, 86, 70, 50, 227, 247, 250, 145, 90, 15, 137, 62, 3, 246, 117, 181, 127, 220, 2, 17, 0, 0, 0, 4, 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