Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85a661f17f5e464ac2ee818ab05aa1e7c1d45ff384e1d0d25c20c7da091d65db

Tx prefix hash: cf3a520b8833601cc6a68b05fa8f4b8ec0299843aa4d8a1628c6625afa9881a0
Tx public key: 4130ff6ac30d4e09dfc7a1932097e48afc14c555848e6a3b3f6d91b1f820b0ad
Timestamp: 1711409095 Timestamp [UCT]: 2024-03-25 23:24:55 Age [y:d:h:m:s]: 01:019:05:40:33
Block: 986360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274712 RingCT/type: yes/0
Extra: 014130ff6ac30d4e09dfc7a1932097e48afc14c555848e6a3b3f6d91b1f820b0ad02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3a9b5d54c9041b12a721a769085a604f1fca3e0d24acf848fe6b9e4697a84f0 0.600000000000 1446589 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": 986370, "vin": [ { "gen": { "height": 986360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3a9b5d54c9041b12a721a769085a604f1fca3e0d24acf848fe6b9e4697a84f0" } } ], "extra": [ 1, 65, 48, 255, 106, 195, 13, 78, 9, 223, 199, 161, 147, 32, 151, 228, 138, 252, 20, 197, 85, 132, 142, 106, 59, 63, 109, 145, 177, 248, 32, 176, 173, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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