Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7a3d066ceb5a3fb64223329e08315d9d893cf48fea85d9205ef799391929072

Tx prefix hash: d374b23ff3c2181d0c400c78c588cb3309a4b2c313f2c4e33efc6a34702e731a
Tx public key: fcf057aa937e72708743a3e887a67000cdae27f4f4775af9635f8d36cb2fa53b
Timestamp: 1697298409 Timestamp [UCT]: 2023-10-14 15:46:49 Age [y:d:h:m:s]: 01:109:20:57:00
Block: 869547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339529 RingCT/type: yes/0
Extra: 01fcf057aa937e72708743a3e887a67000cdae27f4f4775af9635f8d36cb2fa53b02110000000833af99f4000000000000000000

1 output(s) for total of 0.806918831000 dcy

stealth address amount amount idx
00: 91569b96462e2d4e18e2ebec9ebb0d9ec49b723b30d0e90e2a7d302cd742161a 0.806918831000 1324396 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": 869557, "vin": [ { "gen": { "height": 869547 } } ], "vout": [ { "amount": 806918831, "target": { "key": "91569b96462e2d4e18e2ebec9ebb0d9ec49b723b30d0e90e2a7d302cd742161a" } } ], "extra": [ 1, 252, 240, 87, 170, 147, 126, 114, 112, 135, 67, 163, 232, 135, 166, 112, 0, 205, 174, 39, 244, 244, 119, 90, 249, 99, 95, 141, 54, 203, 47, 165, 59, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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