Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cd2551f75ada41a6058200be20ef5de25d5405f9b9ccd40aa1e1e6a3297fb93

Tx prefix hash: 2f8c3d0d756488ec4f4d26082a5478362bd69113952059a0d884879986e8610e
Tx public key: 4ac1e037e8e009fd2d730694522afbb94f00f3aed76f05586a44a52cd9e6371d
Timestamp: 1715567286 Timestamp [UCT]: 2024-05-13 02:28:06 Age [y:d:h:m:s]: 01:177:14:06:08
Block: 1020828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385494 RingCT/type: yes/0
Extra: 014ac1e037e8e009fd2d730694522afbb94f00f3aed76f05586a44a52cd9e6371d02110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f959e86a390f5e8f98bce8c2ca30a5de9c47f1ace030751782471a0a4856b99e 0.600000000000 1484933 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": 1020838, "vin": [ { "gen": { "height": 1020828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f959e86a390f5e8f98bce8c2ca30a5de9c47f1ace030751782471a0a4856b99e" } } ], "extra": [ 1, 74, 193, 224, 55, 232, 224, 9, 253, 45, 115, 6, 148, 82, 42, 251, 185, 79, 0, 243, 174, 215, 111, 5, 88, 106, 68, 165, 44, 217, 230, 55, 29, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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