Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e706aa7ff55dddc79323892ab35f7569a10abce3e3c53abf89759e32a468b1e

Tx prefix hash: 39829ca88c632af474274e71e2e04fd9a40c56f5d227f72ec35a0bb3d3a5de60
Tx public key: 2c5c1087ecdcb1b7b4e7ef86db691badcb8614abb0a8b2aa767b7ea1e810ed8c
Timestamp: 1736275206 Timestamp [UCT]: 2025-01-07 18:40:06 Age [y:d:h:m:s]: 00:296:06:29:13
Block: 1192348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209250 RingCT/type: yes/0
Extra: 012c5c1087ecdcb1b7b4e7ef86db691badcb8614abb0a8b2aa767b7ea1e810ed8c021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb9570aa3573b18d7019b3f3ae633a16c00b605acc215ae8654d33483cba8cec 0.600000000000 1678897 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": 1192358, "vin": [ { "gen": { "height": 1192348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb9570aa3573b18d7019b3f3ae633a16c00b605acc215ae8654d33483cba8cec" } } ], "extra": [ 1, 44, 92, 16, 135, 236, 220, 177, 183, 180, 231, 239, 134, 219, 105, 27, 173, 203, 134, 20, 171, 176, 168, 178, 170, 118, 123, 126, 161, 232, 16, 237, 140, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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