Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dbfe4acee84c239607f00c17d2137d1af02e0963a5fb2a5bacb899b5c20c922

Tx prefix hash: f27a252771da9b2feeff4ad785f386cbc3755a0738bbcfe4e0f975e620d736a1
Tx public key: c43706f1409b391e029c99184f8cc46575d3c051839f4d0a2227a7f4f078c97c
Timestamp: 1736255321 Timestamp [UCT]: 2025-01-07 13:08:41 Age [y:d:h:m:s]: 00:093:05:30:55
Block: 1192183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66417 RingCT/type: yes/0
Extra: 01c43706f1409b391e029c99184f8cc46575d3c051839f4d0a2227a7f4f078c97c0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f84b1209bb08a98dd0aa6ed65aa896851a2bbbb1da248eb36417d04572590eaa 0.600000000000 1678732 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": 1192193, "vin": [ { "gen": { "height": 1192183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f84b1209bb08a98dd0aa6ed65aa896851a2bbbb1da248eb36417d04572590eaa" } } ], "extra": [ 1, 196, 55, 6, 241, 64, 155, 57, 30, 2, 156, 153, 24, 79, 140, 196, 101, 117, 211, 192, 81, 131, 159, 77, 10, 34, 39, 167, 244, 240, 120, 201, 124, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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