Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 971d4d9aa8b9efcafc9fc5083acd82b0e374271ad27b04778501629dd4a162ae

Tx prefix hash: 8577e526dce00117186c8049ce1f242db6e5583d07195f89cd73359384093b34
Tx public key: d036c897a7adbdc5ffccd043613101d96ae54e52bde6bcb9ed2eb080c8bfdb2d
Timestamp: 1719947325 Timestamp [UCT]: 2024-07-02 19:08:45 Age [y:d:h:m:s]: 00:281:09:07:37
Block: 1057121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201054 RingCT/type: yes/0
Extra: 01d036c897a7adbdc5ffccd043613101d96ae54e52bde6bcb9ed2eb080c8bfdb2d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cefff8b25740293c9436f2fe9e8a169d2d18cbfe3c95eb3824e308394093dfa 0.600000000000 1527552 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": 1057131, "vin": [ { "gen": { "height": 1057121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cefff8b25740293c9436f2fe9e8a169d2d18cbfe3c95eb3824e308394093dfa" } } ], "extra": [ 1, 208, 54, 200, 151, 167, 173, 189, 197, 255, 204, 208, 67, 97, 49, 1, 217, 106, 229, 78, 82, 189, 230, 188, 185, 237, 46, 176, 128, 200, 191, 219, 45, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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