Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dce528c24ea202fe01d1077380414d994417246e6f2409775aae6d53c45ae730

Tx prefix hash: 5ce9ae601b63d40215365cf1f6ee7d9e81b4c82aae271a2ae03e8b93b5521149
Tx public key: c7e5dd4033e848cdd304fd0fb5a42869cb2cc1bec796ec87504aac5f6e2c5930
Timestamp: 1708413920 Timestamp [UCT]: 2024-02-20 07:25:20 Age [y:d:h:m:s]: 01:087:10:24:09
Block: 961499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323545 RingCT/type: yes/0
Extra: 01c7e5dd4033e848cdd304fd0fb5a42869cb2cc1bec796ec87504aac5f6e2c593002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 670f9fc7906dc5ca0710d8a806e4f06edf13114d015b7ccc4af8299b2fd9e0a6 0.600000000000 1421110 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": 961509, "vin": [ { "gen": { "height": 961499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "670f9fc7906dc5ca0710d8a806e4f06edf13114d015b7ccc4af8299b2fd9e0a6" } } ], "extra": [ 1, 199, 229, 221, 64, 51, 232, 72, 205, 211, 4, 253, 15, 181, 164, 40, 105, 203, 44, 193, 190, 199, 150, 236, 135, 80, 74, 172, 95, 110, 44, 89, 48, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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