Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d0099d55ee0f1b9e46e4912be024d512f63c904ab33d0f1e39b5672834c10e6

Tx prefix hash: 3bc8bfc5de173035ded5eb754b558bb78918d1c9ab85540d6d85c1788663ef70
Tx public key: b563425dbf7a507c5a1a4d24518729ffa3df396461d8ddc5aeb3fc54cfd5d33a
Timestamp: 1713070390 Timestamp [UCT]: 2024-04-14 04:53:10 Age [y:d:h:m:s]: 00:258:11:43:54
Block: 1000083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185049 RingCT/type: yes/0
Extra: 01b563425dbf7a507c5a1a4d24518729ffa3df396461d8ddc5aeb3fc54cfd5d33a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1820587d853a50cd64c7d696a3c1e00319120b58aee3e97fec73f8813a42061 0.600000000000 1460573 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": 1000093, "vin": [ { "gen": { "height": 1000083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1820587d853a50cd64c7d696a3c1e00319120b58aee3e97fec73f8813a42061" } } ], "extra": [ 1, 181, 99, 66, 93, 191, 122, 80, 124, 90, 26, 77, 36, 81, 135, 41, 255, 163, 223, 57, 100, 97, 216, 221, 197, 174, 179, 252, 84, 207, 213, 211, 58, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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