Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e4d5a12e01c09f833576507a0094593b510186fc970ef8df1413b1c9c9dd59c

Tx prefix hash: ad3a8e35e80cba313e858bfed47cc21da172952a4032c3c238d91104d02d7514
Tx public key: f1dcbc263c909bda3b15ef37515be6b45491b7be2750186d23d1edc6e93797e7
Timestamp: 1722438615 Timestamp [UCT]: 2024-07-31 15:10:15 Age [y:d:h:m:s]: 00:182:03:09:45
Block: 1077771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130051 RingCT/type: yes/0
Extra: 01f1dcbc263c909bda3b15ef37515be6b45491b7be2750186d23d1edc6e93797e702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e58fe69f766067fd53d5d3120e42636a5b2984e92701015a28a59446d5c4690 0.600000000000 1550326 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": 1077781, "vin": [ { "gen": { "height": 1077771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e58fe69f766067fd53d5d3120e42636a5b2984e92701015a28a59446d5c4690" } } ], "extra": [ 1, 241, 220, 188, 38, 60, 144, 155, 218, 59, 21, 239, 55, 81, 91, 230, 180, 84, 145, 183, 190, 39, 80, 24, 109, 35, 209, 237, 198, 233, 55, 151, 231, 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