Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f754aea137cf7a8f47ccdbe2ee3da84884feb10961521f0b31dd73dfc0481a75

Tx prefix hash: 003567e65c77450abbdb20781a6611cb7d918afa83643350b8ebe69e9daaa841
Tx public key: f36f6f7e61b9565b2562a28472ab867b4bc13df27d3cc0fedd0d803ac003d37a
Timestamp: 1681930891 Timestamp [UCT]: 2023-04-19 19:01:31 Age [y:d:h:m:s]: 01:168:23:28:34
Block: 742185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382256 RingCT/type: yes/0
Extra: 01f36f6f7e61b9565b2562a28472ab867b4bc13df27d3cc0fedd0d803ac003d37a02110000000275e3f0e9000000000000000000

1 output(s) for total of 2.132225898000 dcy

stealth address amount amount idx
00: f658ccad0b3f2d16d821563bc61993d081c528ca08df841bebe9d920995b0f38 2.132225898000 1189144 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": 742195, "vin": [ { "gen": { "height": 742185 } } ], "vout": [ { "amount": 2132225898, "target": { "key": "f658ccad0b3f2d16d821563bc61993d081c528ca08df841bebe9d920995b0f38" } } ], "extra": [ 1, 243, 111, 111, 126, 97, 185, 86, 91, 37, 98, 162, 132, 114, 171, 134, 123, 75, 193, 61, 242, 125, 60, 192, 254, 221, 13, 128, 58, 192, 3, 211, 122, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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