Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ee384a4d715df730823910dfcce008fd6115a766c5c82b508c0f91ca1c062a3

Tx prefix hash: 592e57354a8a59f4a1381a1aa0c41d44c63358027be1ecdd6257a4fd6e93009f
Tx public key: da90f39b70afe176c488153c92befb7409e8737505293bc95c642827bb364740
Timestamp: 1580755288 Timestamp [UCT]: 2020-02-03 18:41:28 Age [y:d:h:m:s]: 05:099:06:24:40
Block: 57902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1223059 RingCT/type: yes/0
Extra: 01da90f39b70afe176c488153c92befb7409e8737505293bc95c642827bb36474002110000002b4943cd9f000000000000000000

1 output(s) for total of 394.591257751000 dcy

stealth address amount amount idx
00: 9999cb55fc94a0e0aa3b8f7b5acba35aa41f6d80627334024bec4a124f43600f 394.591257751000 107081 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": 57912, "vin": [ { "gen": { "height": 57902 } } ], "vout": [ { "amount": 394591257751, "target": { "key": "9999cb55fc94a0e0aa3b8f7b5acba35aa41f6d80627334024bec4a124f43600f" } } ], "extra": [ 1, 218, 144, 243, 155, 112, 175, 225, 118, 196, 136, 21, 60, 146, 190, 251, 116, 9, 232, 115, 117, 5, 41, 59, 201, 92, 100, 40, 39, 187, 54, 71, 64, 2, 17, 0, 0, 0, 43, 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