Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3112aa218903021d852aced1a963f1db75484165aadfc9c665584dda6bc1ac8

Tx prefix hash: 0fabbad99670f12564fb7782deedb123d5b0bd606daa4b64909339f69869e23e
Tx public key: 0278e0e81c1fd0e0f2cec9275a2c91c1ad6bc46ab32788aa85d6fc794e436611
Timestamp: 1703525224 Timestamp [UCT]: 2023-12-25 17:27:04 Age [y:d:h:m:s]: 01:173:10:24:08
Block: 920974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385013 RingCT/type: yes/0
Extra: 010278e0e81c1fd0e0f2cec9275a2c91c1ad6bc46ab32788aa85d6fc794e4366110211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bebade5a0ada0d5a7aac5d26f485a94f4f3238f8a6c8590fbffabc0c9e6eda1 0.600000000000 1378658 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": 920984, "vin": [ { "gen": { "height": 920974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bebade5a0ada0d5a7aac5d26f485a94f4f3238f8a6c8590fbffabc0c9e6eda1" } } ], "extra": [ 1, 2, 120, 224, 232, 28, 31, 208, 224, 242, 206, 201, 39, 90, 44, 145, 193, 173, 107, 196, 106, 179, 39, 136, 170, 133, 214, 252, 121, 78, 67, 102, 17, 2, 17, 0, 0, 0, 1, 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