Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53bc856612e6a8d8e1cf2e2425d78d7f4cc7c9f816e40cbadf39f53f386bf39d

Tx prefix hash: 486f52ea5c9bc68a37aec963690f4147286458dfdb24fbcac330bfe5a0817ba2
Tx public key: 90d765ea1a9c0c45e31d6484b7a7afd879ce57e317278c753d7bff36a4850051
Timestamp: 1717359698 Timestamp [UCT]: 2024-06-02 20:21:38 Age [y:d:h:m:s]: 00:266:02:42:19
Block: 1035666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190151 RingCT/type: yes/0
Extra: 0190d765ea1a9c0c45e31d6484b7a7afd879ce57e317278c753d7bff36a4850051021100000002162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 510936a66329fc78e5387f424ce01e4d7a285d50a65121f7f772e68442d722e1 0.600000000000 1504189 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": 1035676, "vin": [ { "gen": { "height": 1035666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "510936a66329fc78e5387f424ce01e4d7a285d50a65121f7f772e68442d722e1" } } ], "extra": [ 1, 144, 215, 101, 234, 26, 156, 12, 69, 227, 29, 100, 132, 183, 167, 175, 216, 121, 206, 87, 227, 23, 39, 140, 117, 61, 123, 255, 54, 164, 133, 0, 81, 2, 17, 0, 0, 0, 2, 22, 38, 19, 170, 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