Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b7bed96a9882c1bd4140e3a27e5e3ca6b47b4cc8fc2b8c2676cbe239ff9a5af

Tx prefix hash: b7f5deff50941cc7db39e8fbcca074e36d0d1341651009cc693172dfa409770b
Tx public key: 0e8ddfa0f1d225776f1d708867fd439d9b17d0505ace5f51b5c406e392919b3b
Timestamp: 1704380948 Timestamp [UCT]: 2024-01-04 15:09:08 Age [y:d:h:m:s]: 01:092:19:37:58
Block: 928069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327437 RingCT/type: yes/0
Extra: 010e8ddfa0f1d225776f1d708867fd439d9b17d0505ace5f51b5c406e392919b3b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7943894d6d42fe452dd30f55bfc3fb94b286624233470f760b790eefc7399f1e 0.600000000000 1385925 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": 928079, "vin": [ { "gen": { "height": 928069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7943894d6d42fe452dd30f55bfc3fb94b286624233470f760b790eefc7399f1e" } } ], "extra": [ 1, 14, 141, 223, 160, 241, 210, 37, 119, 111, 29, 112, 136, 103, 253, 67, 157, 155, 23, 208, 80, 90, 206, 95, 81, 181, 196, 6, 227, 146, 145, 155, 59, 2, 17, 0, 0, 0, 2, 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