Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3786e6ddf2e7f8df923fad2f2fe683f79f7d746627ea4bc985870a29f74e1cb7

Tx prefix hash: 95827ad86a91893b35294e45d64eede52d9e70bf3e0d5cd19ae8e8ff4409de9a
Tx public key: da9fb91f2c63f5b07b9dc436e1fa3fea3264fc31edfdc88e11ca27d1b45387f2
Timestamp: 1578003561 Timestamp [UCT]: 2020-01-02 22:19:21 Age [y:d:h:m:s]: 05:130:12:51:56
Block: 37457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1243094 RingCT/type: yes/0
Extra: 01da9fb91f2c63f5b07b9dc436e1fa3fea3264fc31edfdc88e11ca27d1b45387f20211000000254943cd9f000000000000000000

1 output(s) for total of 461.206452233000 dcy

stealth address amount amount idx
00: 046a57088f6e3d9efed300c2a18040c9af250ad3a54e0cd9cb16e2f07cdf126e 461.206452233000 63591 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": 37467, "vin": [ { "gen": { "height": 37457 } } ], "vout": [ { "amount": 461206452233, "target": { "key": "046a57088f6e3d9efed300c2a18040c9af250ad3a54e0cd9cb16e2f07cdf126e" } } ], "extra": [ 1, 218, 159, 185, 31, 44, 99, 245, 176, 123, 157, 196, 54, 225, 250, 63, 234, 50, 100, 252, 49, 237, 253, 200, 142, 17, 202, 39, 209, 180, 83, 135, 242, 2, 17, 0, 0, 0, 37, 73, 67, 205, 159, 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