Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d1d401eff19920f824e403e3f11eeb88fe54e48f64a1af1a126e258730049e3

Tx prefix hash: 614cee8202ae35b323fb57936093b1b6afe33cddb7e861cd05a9f59ccfe23102
Tx public key: 511a56928d8ff8b5bfaf3717b1eaa2a969668b08a2c3794d1aa0d7aca100db14
Timestamp: 1718126109 Timestamp [UCT]: 2024-06-11 17:15:09 Age [y:d:h:m:s]: 00:173:21:15:59
Block: 1042026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124442 RingCT/type: yes/0
Extra: 01511a56928d8ff8b5bfaf3717b1eaa2a969668b08a2c3794d1aa0d7aca100db140211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca93a29f1957925a0f109fed383327c148396b6ef7f6cd46e55e90fb3dea260f 0.600000000000 1510843 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": 1042036, "vin": [ { "gen": { "height": 1042026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca93a29f1957925a0f109fed383327c148396b6ef7f6cd46e55e90fb3dea260f" } } ], "extra": [ 1, 81, 26, 86, 146, 141, 143, 248, 181, 191, 175, 55, 23, 177, 234, 162, 169, 105, 102, 139, 8, 162, 195, 121, 77, 26, 160, 215, 172, 161, 0, 219, 20, 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