Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd9fa54fe0d8ec7ed45fdad934fd42709fb8027be7205ef4c606b1442536ce8a

Tx prefix hash: 664bb9c3b8179fab3007acf192422e3d81dab37e360628393952d922d87369e2
Tx public key: 18bef33ffd1e0e4baf5d0a0c9d3d6846f28a74956a304bcaf8cc2f115a533ab4
Timestamp: 1732868530 Timestamp [UCT]: 2024-11-29 08:22:10 Age [y:d:h:m:s]: 00:030:09:42:36
Block: 1164145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21741 RingCT/type: yes/0
Extra: 0118bef33ffd1e0e4baf5d0a0c9d3d6846f28a74956a304bcaf8cc2f115a533ab4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a39f101a6d1048ca9749808a3d051fdbc4174fbbc46ba0b084cad2ddc16e1f1 0.600000000000 1649818 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": 1164155, "vin": [ { "gen": { "height": 1164145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a39f101a6d1048ca9749808a3d051fdbc4174fbbc46ba0b084cad2ddc16e1f1" } } ], "extra": [ 1, 24, 190, 243, 63, 253, 30, 14, 75, 175, 93, 10, 12, 157, 61, 104, 70, 242, 138, 116, 149, 106, 48, 75, 202, 248, 204, 47, 17, 90, 83, 58, 180, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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