Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f39c6d1cbe9c633e95327a6d9bd6520d9e072d7c7c85c4b9faf0be2170fd947a

Tx prefix hash: c98a1fb648106fa26799e1674db0be88c8c3c6694a0fed35c2657e473a69cfc0
Tx public key: 7171b3f70a94f06e10e22af49345c09894a1543ba726771407cf7aeaa9c3447c
Timestamp: 1703762672 Timestamp [UCT]: 2023-12-28 11:24:32 Age [y:d:h:m:s]: 01:123:17:27:27
Block: 922939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349566 RingCT/type: yes/0
Extra: 017171b3f70a94f06e10e22af49345c09894a1543ba726771407cf7aeaa9c3447c02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbf09a11e3887fccc80e7d962f66113f127f76cb33463356dff40636e59de3bf 0.600000000000 1380645 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": 922949, "vin": [ { "gen": { "height": 922939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbf09a11e3887fccc80e7d962f66113f127f76cb33463356dff40636e59de3bf" } } ], "extra": [ 1, 113, 113, 179, 247, 10, 148, 240, 110, 16, 226, 42, 244, 147, 69, 192, 152, 148, 161, 84, 59, 167, 38, 119, 20, 7, 207, 122, 234, 169, 195, 68, 124, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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