Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a4a45d017028f154faabd83e48afc79aee819d7be126e2aa0a52bd649909abf

Tx prefix hash: 65fc958986c69979c8112266962d1965f16a18b6e94ad444668cbdc14d87132a
Tx public key: e6a06277a45f3d446de0c103e2cb692aea64320a15cd7e50cddb0a8936a33b6d
Timestamp: 1721750627 Timestamp [UCT]: 2024-07-23 16:03:47 Age [y:d:h:m:s]: 00:262:08:20:22
Block: 1072057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187432 RingCT/type: yes/0
Extra: 01e6a06277a45f3d446de0c103e2cb692aea64320a15cd7e50cddb0a8936a33b6d02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69c0a2f2fc7a209b3cc4889281c33426e7d2acb43183915898a7fb669287fba5 0.600000000000 1544492 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": 1072067, "vin": [ { "gen": { "height": 1072057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69c0a2f2fc7a209b3cc4889281c33426e7d2acb43183915898a7fb669287fba5" } } ], "extra": [ 1, 230, 160, 98, 119, 164, 95, 61, 68, 109, 224, 193, 3, 226, 203, 105, 42, 234, 100, 50, 10, 21, 205, 126, 80, 205, 219, 10, 137, 54, 163, 59, 109, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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