Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4190726607c94f6699db7429b97e9d546d7e892134af612c82edc69257403cf7

Tx prefix hash: 3aa82accf2dc6a6ef1f1f7230cfa0e7fffba470e7ae40e07b3e680fb7b3d68ea
Tx public key: 0f390f5594c8c81a126144853764b4dc39b95962e8142fe1c00272a2f26ef5a6
Timestamp: 1676461655 Timestamp [UCT]: 2023-02-15 11:47:35 Age [y:d:h:m:s]: 01:348:12:18:21
Block: 697487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509788 RingCT/type: yes/0
Extra: 010f390f5594c8c81a126144853764b4dc39b95962e8142fe1c00272a2f26ef5a602110000000174b6d784000000000000000000

1 output(s) for total of 2.998720201000 dcy

stealth address amount amount idx
00: b7b4f07c49d878a2f8f4e63a99cb55e89160e8d9ae93b3709ca7b1ca069c98b3 2.998720201000 1140682 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": 697497, "vin": [ { "gen": { "height": 697487 } } ], "vout": [ { "amount": 2998720201, "target": { "key": "b7b4f07c49d878a2f8f4e63a99cb55e89160e8d9ae93b3709ca7b1ca069c98b3" } } ], "extra": [ 1, 15, 57, 15, 85, 148, 200, 200, 26, 18, 97, 68, 133, 55, 100, 180, 220, 57, 185, 89, 98, 232, 20, 47, 225, 192, 2, 114, 162, 242, 110, 245, 166, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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