Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ba7c154c713e872082f85fcb3489b8890ce85287dc54630cf6ff62270f93b68

Tx prefix hash: 1f1e3c7fd215a89d1ae29869ffe3b01931215cffa4dc11b465cb0c376a7171d3
Tx public key: 2765b7e2a75498d6528d9861ec8c18127d5f5be33b4620ef8fe37c96b98abfaf
Timestamp: 1727382735 Timestamp [UCT]: 2024-09-26 20:32:15 Age [y:d:h:m:s]: 00:189:08:18:14
Block: 1118758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135132 RingCT/type: yes/0
Extra: 012765b7e2a75498d6528d9861ec8c18127d5f5be33b4620ef8fe37c96b98abfaf021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e315530acb04cd2c628f49ab6f00ab4110f079a3df1d635d48868905d511a77a 0.600000000000 1600065 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": 1118768, "vin": [ { "gen": { "height": 1118758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e315530acb04cd2c628f49ab6f00ab4110f079a3df1d635d48868905d511a77a" } } ], "extra": [ 1, 39, 101, 183, 226, 167, 84, 152, 214, 82, 141, 152, 97, 236, 140, 24, 18, 125, 95, 91, 227, 59, 70, 32, 239, 143, 227, 124, 150, 185, 138, 191, 175, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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