Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d44a8bce37f2d981872db2003f72efc6ae77a2ee0b9aace16ad73bba9076e14c

Tx prefix hash: 9c37e7d69a74cfd07deffa9cf23b3a2e9333e28dde5e8163e9ab8e2c137d6e00
Tx public key: c3704b1ae5880d7b900316ba3756083f6dd79b0a1bdf0c8e454746a3a52e2a68
Timestamp: 1709474731 Timestamp [UCT]: 2024-03-03 14:05:31 Age [y:d:h:m:s]: 01:277:20:37:03
Block: 970302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457332 RingCT/type: yes/0
Extra: 01c3704b1ae5880d7b900316ba3756083f6dd79b0a1bdf0c8e454746a3a52e2a680211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e481f6fc860be66c109d0023104251a538a9d4e3922d9d4f8bb9379c3c8b819 0.600000000000 1430153 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": 970312, "vin": [ { "gen": { "height": 970302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e481f6fc860be66c109d0023104251a538a9d4e3922d9d4f8bb9379c3c8b819" } } ], "extra": [ 1, 195, 112, 75, 26, 229, 136, 13, 123, 144, 3, 22, 186, 55, 86, 8, 63, 109, 215, 155, 10, 27, 223, 12, 142, 69, 71, 70, 163, 165, 46, 42, 104, 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