Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f39223731a64cc3c23e9324f5c9b4076e979ac804652582e6a6a81051df83047

Tx prefix hash: 6d095034def3602a481ca012677605b4c33ac6295e8193655b8fa5ac6228bb61
Tx public key: c9f822e87a933dc43bf6142826eba8efd7fa75f2aff39c4b66fdaff2ff9c21ab
Timestamp: 1645462791 Timestamp [UCT]: 2022-02-21 16:59:51 Age [y:d:h:m:s]: 02:257:12:11:20
Block: 443478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 703386 RingCT/type: yes/0
Extra: 01c9f822e87a933dc43bf6142826eba8efd7fa75f2aff39c4b66fdaff2ff9c21ab0211000000014a0f5013000000000000000000

1 output(s) for total of 20.826871817000 dcy

stealth address amount amount idx
00: f2f35c771ba2717779fa714fc7b0cc1fd6d7705d4d351496e0940373ad1318cc 20.826871817000 856517 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": 443488, "vin": [ { "gen": { "height": 443478 } } ], "vout": [ { "amount": 20826871817, "target": { "key": "f2f35c771ba2717779fa714fc7b0cc1fd6d7705d4d351496e0940373ad1318cc" } } ], "extra": [ 1, 201, 248, 34, 232, 122, 147, 61, 196, 59, 246, 20, 40, 38, 235, 168, 239, 215, 250, 117, 242, 175, 243, 156, 75, 102, 253, 175, 242, 255, 156, 33, 171, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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