Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e87e97fdfb529d6e09f4ec86a1fd5a7717dbe9c6caa1760b86c559000dd01ce

Tx prefix hash: e7b0e992b3cc957df327a82f70576e9b7e2018e0b95a4cee559dd0da616859b0
Tx public key: a157bdc6c5e1b56c5f5217c1e07ccd53c9ef1c030bff694031777b10dbad1cf1
Timestamp: 1636667627 Timestamp [UCT]: 2021-11-11 21:53:47 Age [y:d:h:m:s]: 03:048:07:40:59
Block: 372377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 813139 RingCT/type: yes/0
Extra: 01a157bdc6c5e1b56c5f5217c1e07ccd53c9ef1c030bff694031777b10dbad1cf102110000000a1154028c000000000000000000

1 output(s) for total of 35.822905612000 dcy

stealth address amount amount idx
00: 449e3c22fca45b04fd4cef4a560fa3103c2c5687970c71baebfcea911eae4060 35.822905612000 754339 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": 372387, "vin": [ { "gen": { "height": 372377 } } ], "vout": [ { "amount": 35822905612, "target": { "key": "449e3c22fca45b04fd4cef4a560fa3103c2c5687970c71baebfcea911eae4060" } } ], "extra": [ 1, 161, 87, 189, 198, 197, 225, 181, 108, 95, 82, 23, 193, 224, 124, 205, 83, 201, 239, 28, 3, 11, 255, 105, 64, 49, 119, 123, 16, 219, 173, 28, 241, 2, 17, 0, 0, 0, 10, 17, 84, 2, 140, 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