Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a51e4376e607a89f0c71cbd19800aa37fd2d9410dfc5d6b25b29a4c1156a62f3

Tx prefix hash: 66ca04c4eeda37efb656e0ee38138cd118280388a8dc75a94214016033f22f0d
Tx public key: 80668b8c0330a8ad4d6468a51b3cd2ff6c5f6e2a98ea639a3d5597390427debf
Timestamp: 1722608606 Timestamp [UCT]: 2024-08-02 14:23:26 Age [y:d:h:m:s]: 00:258:13:00:04
Block: 1079185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184678 RingCT/type: yes/0
Extra: 0180668b8c0330a8ad4d6468a51b3cd2ff6c5f6e2a98ea639a3d5597390427debf021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a97e97335fd8761633ea065ac0b499ce59e9ba790a75b6d1358da9befa55c4e 0.600000000000 1552028 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": 1079195, "vin": [ { "gen": { "height": 1079185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a97e97335fd8761633ea065ac0b499ce59e9ba790a75b6d1358da9befa55c4e" } } ], "extra": [ 1, 128, 102, 139, 140, 3, 48, 168, 173, 77, 100, 104, 165, 27, 60, 210, 255, 108, 95, 110, 42, 152, 234, 99, 154, 61, 85, 151, 57, 4, 39, 222, 191, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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