Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14ab8597c14097cf637d4495a1ed7405324099ff722e721878b1a0d1c41c8e32

Tx prefix hash: efd29602d90a3642b10f5fe167aac865b42323aa489e7401752640f46c91ef23
Tx public key: 51e265e01d9c2b2d12618c3d8b8f712599fd54d48e282ccbd870e63aaf7f6b93
Timestamp: 1704997040 Timestamp [UCT]: 2024-01-11 18:17:20 Age [y:d:h:m:s]: 01:094:09:21:13
Block: 933157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328574 RingCT/type: yes/0
Extra: 0151e265e01d9c2b2d12618c3d8b8f712599fd54d48e282ccbd870e63aaf7f6b9302110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96581c9dbdb2141ec0fb2f9716d484acb9ca5a85c3a5a1723702945107ef8f78 0.600000000000 1391113 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": 933167, "vin": [ { "gen": { "height": 933157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96581c9dbdb2141ec0fb2f9716d484acb9ca5a85c3a5a1723702945107ef8f78" } } ], "extra": [ 1, 81, 226, 101, 224, 29, 156, 43, 45, 18, 97, 140, 61, 139, 143, 113, 37, 153, 253, 84, 212, 142, 40, 44, 203, 216, 112, 230, 58, 175, 127, 107, 147, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 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