Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89a8c7015ebfa9c7247c9dc56abf53033fb278a1b765ca6a960c79a994b3085d

Tx prefix hash: 9e27e92819696211a8e404a5095eab660da6a0f42ca1b156aaaa6b05e873926a
Tx public key: 9cb6ebd7e0e401d6ae29cc3e3d8e0bef94d4f8334f658dad69822366c01f7469
Timestamp: 1699489038 Timestamp [UCT]: 2023-11-09 00:17:18 Age [y:d:h:m:s]: 01:149:22:03:58
Block: 887517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368315 RingCT/type: yes/0
Extra: 019cb6ebd7e0e401d6ae29cc3e3d8e0bef94d4f8334f658dad69822366c01f7469021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.703538316000 dcy

stealth address amount amount idx
00: fd595edf316f683c64717cf11a5f90a9f023fd7041e69eb8a7df56b7b19ebfa1 0.703538316000 1343402 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": 887527, "vin": [ { "gen": { "height": 887517 } } ], "vout": [ { "amount": 703538316, "target": { "key": "fd595edf316f683c64717cf11a5f90a9f023fd7041e69eb8a7df56b7b19ebfa1" } } ], "extra": [ 1, 156, 182, 235, 215, 224, 228, 1, 214, 174, 41, 204, 62, 61, 142, 11, 239, 148, 212, 248, 51, 79, 101, 141, 173, 105, 130, 35, 102, 192, 31, 116, 105, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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