Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb57af479b962bf951e3f783c0a62f7d99633e682d6b80cf6c696db377e93f31

Tx prefix hash: fd08a7b609d96a5393f5f7a9de2be7b2728034461f319e320ca1019ed177bc5e
Tx public key: e5668d74f687a88a4f4373bbb0de09e7a83e76a686af8e9e7eaff0d823a2aece
Timestamp: 1678376760 Timestamp [UCT]: 2023-03-09 15:46:00 Age [y:d:h:m:s]: 01:309:09:17:40
Block: 713370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482029 RingCT/type: yes/0
Extra: 01e5668d74f687a88a4f4373bbb0de09e7a83e76a686af8e9e7eaff0d823a2aece0211000000075029cbac000000000000000000

1 output(s) for total of 2.656494675000 dcy

stealth address amount amount idx
00: 771bfb82bf53334e9443a6fdbdb3aecd624286b8c57ffe280d43336f1ce81437 2.656494675000 1157597 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": 713380, "vin": [ { "gen": { "height": 713370 } } ], "vout": [ { "amount": 2656494675, "target": { "key": "771bfb82bf53334e9443a6fdbdb3aecd624286b8c57ffe280d43336f1ce81437" } } ], "extra": [ 1, 229, 102, 141, 116, 246, 135, 168, 138, 79, 67, 115, 187, 176, 222, 9, 231, 168, 62, 118, 166, 134, 175, 142, 158, 126, 175, 240, 216, 35, 162, 174, 206, 2, 17, 0, 0, 0, 7, 80, 41, 203, 172, 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