Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28ef5aa742db6213ca077fdd02fb0ab784197b99113273c82517848e16b5e99f

Tx prefix hash: 0296a93adf48c5a4f77c3c673652709ad9780ccba05cdf50a5e0a5df1cf23618
Tx public key: edab6964fd7a21d293d0aacab72f71900a95af475e11d9b39e93a5bccd1978e6
Timestamp: 1707625237 Timestamp [UCT]: 2024-02-11 04:20:37 Age [y:d:h:m:s]: 01:157:00:39:52
Block: 954953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372233 RingCT/type: yes/0
Extra: 01edab6964fd7a21d293d0aacab72f71900a95af475e11d9b39e93a5bccd1978e602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84c24e452b0ad9c2d959b0ad45a19685b3d128d8c6059f758fdb051ff67fc7a8 0.600000000000 1414235 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": 954963, "vin": [ { "gen": { "height": 954953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84c24e452b0ad9c2d959b0ad45a19685b3d128d8c6059f758fdb051ff67fc7a8" } } ], "extra": [ 1, 237, 171, 105, 100, 253, 122, 33, 210, 147, 208, 170, 202, 183, 47, 113, 144, 10, 149, 175, 71, 94, 17, 217, 179, 158, 147, 165, 188, 205, 25, 120, 230, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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