Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e1fbd608d7952e2e1ce52e3f27669a395174b7a6b35ef10b09937582e80b8e8

Tx prefix hash: be2a8a7df3ec62c988a1ab05c52e22301c0e619fa7ba4decd4898e665a9c6127
Tx public key: 8b1795c086bfba26b92b919d2cdf13b05de2fa2c787e4cceb085b73aa5417e52
Timestamp: 1720921087 Timestamp [UCT]: 2024-07-14 01:38:07 Age [y:d:h:m:s]: 00:224:19:07:47
Block: 1065206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160542 RingCT/type: yes/0
Extra: 018b1795c086bfba26b92b919d2cdf13b05de2fa2c787e4cceb085b73aa5417e5202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c6667f560da1c6a6fca673a899d0fa0006f4f32ddafa606aca7586e3937f446 0.600000000000 1535751 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": 1065216, "vin": [ { "gen": { "height": 1065206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c6667f560da1c6a6fca673a899d0fa0006f4f32ddafa606aca7586e3937f446" } } ], "extra": [ 1, 139, 23, 149, 192, 134, 191, 186, 38, 185, 43, 145, 157, 44, 223, 19, 176, 93, 226, 250, 44, 120, 126, 76, 206, 176, 133, 183, 58, 165, 65, 126, 82, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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