Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbbffbfab188a9ee5f79d249d8f84d9f36ad0fa367a8e2b49f3d9c9c5e657935

Tx prefix hash: dd5be160630f20f9b82c0d1d0a05d10c609253b40699d608f555423f43afd893
Tx public key: 072411e61e62ecbbc52959c8d91ec32f2cd516a944ad5f16f8bc9fc61e7cd2b0
Timestamp: 1658141138 Timestamp [UCT]: 2022-07-18 10:45:38 Age [y:d:h:m:s]: 02:168:09:23:21
Block: 546374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 641719 RingCT/type: yes/0
Extra: 01072411e61e62ecbbc52959c8d91ec32f2cd516a944ad5f16f8bc9fc61e7cd2b0021100000009c9067537000000000000000000

1 output(s) for total of 9.498089661000 dcy

stealth address amount amount idx
00: 65f6ec688f7fb14abead2a0deda525410d88f8b2d7dd1bf2b3bb1d7c5c19a418 9.498089661000 977381 of 0

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": 546384, "vin": [ { "gen": { "height": 546374 } } ], "vout": [ { "amount": 9498089661, "target": { "key": "65f6ec688f7fb14abead2a0deda525410d88f8b2d7dd1bf2b3bb1d7c5c19a418" } } ], "extra": [ 1, 7, 36, 17, 230, 30, 98, 236, 187, 197, 41, 89, 200, 217, 30, 195, 47, 44, 213, 22, 169, 68, 173, 95, 22, 248, 188, 159, 198, 30, 124, 210, 176, 2, 17, 0, 0, 0, 9, 201, 6, 117, 55, 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