Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb28ccd404b4be53895840d4e6e50e4ffa04f30f72f302ed60d3a467be380ce3

Tx prefix hash: ccbf2135344d926aefe8d150fce4f180e621ac177a29d21a5c4db2a0729da69d
Tx public key: 068868868b2bf3fff44d4eb690d21f6b65a2c31f879e88d5dc5dc8d51e5aaace
Timestamp: 1704371460 Timestamp [UCT]: 2024-01-04 12:31:00 Age [y:d:h:m:s]: 01:055:17:05:10
Block: 927995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300881 RingCT/type: yes/0
Extra: 01068868868b2bf3fff44d4eb690d21f6b65a2c31f879e88d5dc5dc8d51e5aaace02110000000279bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f8f375ebd3417121d40688c7ec751373ed8dbaf6657615defd6b2334e95c130 0.600000000000 1385843 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": 928005, "vin": [ { "gen": { "height": 927995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f8f375ebd3417121d40688c7ec751373ed8dbaf6657615defd6b2334e95c130" } } ], "extra": [ 1, 6, 136, 104, 134, 139, 43, 243, 255, 244, 77, 78, 182, 144, 210, 31, 107, 101, 162, 195, 31, 135, 158, 136, 213, 220, 93, 200, 213, 30, 90, 170, 206, 2, 17, 0, 0, 0, 2, 121, 189, 163, 190, 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