Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87853d1ddcd3128ffd5eb07d0c13a04851445b7d9f91e539c2ac28629338b824

Tx prefix hash: 86aa243106ea1f63a965d81797c1c29fcda0b938c26a51575f06e6e1010a0a43
Tx public key: 9a0a46b742dd88929694ecac772cf3969d978819c9e0827a55f5f8bcce19d171
Timestamp: 1726838939 Timestamp [UCT]: 2024-09-20 13:28:59 Age [y:d:h:m:s]: 00:177:16:35:05
Block: 1114253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126823 RingCT/type: yes/0
Extra: 019a0a46b742dd88929694ecac772cf3969d978819c9e0827a55f5f8bcce19d1710211000000012c3a34dc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 369e0d9d3e946d7c9c236ecea1aeac5a7bf7967243a1afca4a6622cc81219727 0.600000000000 1594052 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": 1114263, "vin": [ { "gen": { "height": 1114253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "369e0d9d3e946d7c9c236ecea1aeac5a7bf7967243a1afca4a6622cc81219727" } } ], "extra": [ 1, 154, 10, 70, 183, 66, 221, 136, 146, 150, 148, 236, 172, 119, 44, 243, 150, 157, 151, 136, 25, 201, 224, 130, 122, 85, 245, 248, 188, 206, 25, 209, 113, 2, 17, 0, 0, 0, 1, 44, 58, 52, 220, 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