Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33db3d75f14a98f2750e4ed1b91039c9fc269db177877a04dab4964e80a736ae

Tx prefix hash: bd0941ac5f833efe9a2b58469989786f1dd430433e35872a16c7d7d5be80dc81
Tx public key: dd584b1a5be7fdfbac0107fcbba78286545e11e090038dfbd9bead7d836c53c2
Timestamp: 1694637876 Timestamp [UCT]: 2023-09-13 20:44:36 Age [y:d:h:m:s]: 01:227:13:24:03
Block: 847474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423757 RingCT/type: yes/0
Extra: 01dd584b1a5be7fdfbac0107fcbba78286545e11e090038dfbd9bead7d836c53c2021100000005faf35c9c000000000000000000

1 output(s) for total of 0.954919793000 dcy

stealth address amount amount idx
00: 8e59bfa452cdf89a8e4c6243c860e7ee488d377e4dd6de02e1a962981e61d54f 0.954919793000 1300998 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": 847484, "vin": [ { "gen": { "height": 847474 } } ], "vout": [ { "amount": 954919793, "target": { "key": "8e59bfa452cdf89a8e4c6243c860e7ee488d377e4dd6de02e1a962981e61d54f" } } ], "extra": [ 1, 221, 88, 75, 26, 91, 231, 253, 251, 172, 1, 7, 252, 187, 167, 130, 134, 84, 94, 17, 224, 144, 3, 141, 251, 217, 190, 173, 125, 131, 108, 83, 194, 2, 17, 0, 0, 0, 5, 250, 243, 92, 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