Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: deb3cda83e08917e5e97ee54bb2b6777b36b28f17c08679dc95e846c1b16cbb6

Tx prefix hash: e984098f87d683a2927afcc435d08e44fbed27b9432b43a3ba1c9c5b5f5961b7
Tx public key: 1a2e23e8e01fe26cf41dd02d75e991a0b35b627e9ce4d159f61191c5a378984e
Timestamp: 1629811735 Timestamp [UCT]: 2021-08-24 13:28:55 Age [y:d:h:m:s]: 03:262:08:05:14
Block: 319875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 961700 RingCT/type: yes/0
Extra: 011a2e23e8e01fe26cf41dd02d75e991a0b35b627e9ce4d159f61191c5a378984e02110000001151fa4013000000000000000000

1 output(s) for total of 53.471430153000 dcy

stealth address amount amount idx
00: 8c761c3b1e770b67d4e69f313c7d3e2214bce48f696132560dc5174c9fe5c112 53.471430153000 664495 of 0

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": 319885, "vin": [ { "gen": { "height": 319875 } } ], "vout": [ { "amount": 53471430153, "target": { "key": "8c761c3b1e770b67d4e69f313c7d3e2214bce48f696132560dc5174c9fe5c112" } } ], "extra": [ 1, 26, 46, 35, 232, 224, 31, 226, 108, 244, 29, 208, 45, 117, 233, 145, 160, 179, 91, 98, 126, 156, 228, 209, 89, 246, 17, 145, 197, 163, 120, 152, 78, 2, 17, 0, 0, 0, 17, 81, 250, 64, 19, 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