Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e18eed38661d5866c39f69c05385f7e6bd844cae1493086f071a5f68c0ffe14f

Tx prefix hash: af99293cea2b7e2082a34dc904d551dc78a951e6a01192a4f2c076df262c9c7a
Tx public key: 5e08a0eb0a79159a5b0cba4e169a394e845dffc47f265fb6fe472cbe8f9e4a24
Timestamp: 1706808831 Timestamp [UCT]: 2024-02-01 17:33:51 Age [y:d:h:m:s]: 00:287:18:49:51
Block: 948179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206059 RingCT/type: yes/0
Extra: 015e08a0eb0a79159a5b0cba4e169a394e845dffc47f265fb6fe472cbe8f9e4a240211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 696f62422cf4a837741e88fcae1e330ad97d29f937c2d63739071a0f7439a932 0.600000000000 1406551 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": 948189, "vin": [ { "gen": { "height": 948179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "696f62422cf4a837741e88fcae1e330ad97d29f937c2d63739071a0f7439a932" } } ], "extra": [ 1, 94, 8, 160, 235, 10, 121, 21, 154, 91, 12, 186, 78, 22, 154, 57, 78, 132, 93, 255, 196, 127, 38, 95, 182, 254, 71, 44, 190, 143, 158, 74, 36, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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