Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d1757f543e463fccea8baf0a539cca2910d52649fcdb79592bf1a3b11b21d01

Tx prefix hash: 7f53e1909b2c0dde945a34d20af4fad93e30cb9543c5bba788069de83094d89a
Tx public key: 0d6af8cb7c8eacc5d48e10c76ad59c4a94577e87a3a6cf5c7b43e56a94003be7
Timestamp: 1714966827 Timestamp [UCT]: 2024-05-06 03:40:27 Age [y:d:h:m:s]: 00:138:11:13:16
Block: 1015831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99190 RingCT/type: yes/0
Extra: 010d6af8cb7c8eacc5d48e10c76ad59c4a94577e87a3a6cf5c7b43e56a94003be70211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e20994d3b337fe14613f96b8a6fcef9d76a728e54468246923baff9a9ecb0073 0.600000000000 1479274 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": 1015841, "vin": [ { "gen": { "height": 1015831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e20994d3b337fe14613f96b8a6fcef9d76a728e54468246923baff9a9ecb0073" } } ], "extra": [ 1, 13, 106, 248, 203, 124, 142, 172, 197, 212, 142, 16, 199, 106, 213, 156, 74, 148, 87, 126, 135, 163, 166, 207, 92, 123, 67, 229, 106, 148, 0, 59, 231, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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