Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36e184d96a7ad3d3db3a7d7b7b144ffff21aaa62c6e823e74f83499068a87ec2

Tx prefix hash: 1703d7faf26b10853cf13d3d273275d98574feffa57a67a4cbfe81d89e04eb1a
Tx public key: 254bf5f328e1f0005d84e878606f2c9b4cd5225cc44715e08ba319a52a1370f4
Timestamp: 1708526144 Timestamp [UCT]: 2024-02-21 14:35:44 Age [y:d:h:m:s]: 01:029:09:51:19
Block: 962430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282038 RingCT/type: yes/0
Extra: 01254bf5f328e1f0005d84e878606f2c9b4cd5225cc44715e08ba319a52a1370f402110000000f0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63b302904d02e9f9c7f64c635832914dbb04d841c1033af4d8d5c25503253163 0.600000000000 1422065 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": 962440, "vin": [ { "gen": { "height": 962430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63b302904d02e9f9c7f64c635832914dbb04d841c1033af4d8d5c25503253163" } } ], "extra": [ 1, 37, 75, 245, 243, 40, 225, 240, 0, 93, 132, 232, 120, 96, 111, 44, 155, 76, 213, 34, 92, 196, 71, 21, 224, 139, 163, 25, 165, 42, 19, 112, 244, 2, 17, 0, 0, 0, 15, 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