Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ffde473a9e2287f1a8a0df43cf81f9db38dbf79bddd1cf73f4a4df5091cfb78

Tx prefix hash: fbee03901ced119836aef92e2f8149709ac0d60448e6f3756a27b2226d091891
Tx public key: 773f177cca3b8a819d8305746f4a9c12c05d532928a6e57b7b8c5d6178150bbe
Timestamp: 1735475929 Timestamp [UCT]: 2024-12-29 12:38:49 Age [y:d:h:m:s]: 00:083:06:12:40
Block: 1185726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59297 RingCT/type: yes/0
Extra: 01773f177cca3b8a819d8305746f4a9c12c05d532928a6e57b7b8c5d6178150bbe02110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e3244f5908101a4509f3c474ffa25858d11bfb9cdf40b70652441b3dda1bf46 0.600000000000 1672201 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": 1185736, "vin": [ { "gen": { "height": 1185726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e3244f5908101a4509f3c474ffa25858d11bfb9cdf40b70652441b3dda1bf46" } } ], "extra": [ 1, 119, 63, 23, 124, 202, 59, 138, 129, 157, 131, 5, 116, 111, 74, 156, 18, 192, 93, 83, 41, 40, 166, 229, 123, 123, 140, 93, 97, 120, 21, 11, 190, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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