Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de0d935e8e30c3101a49cc9a4439a09b0beb1cdf9761c9fd051c076089aca559

Tx prefix hash: a686c78bdeacde01e911e5e3afa0c30892d98041727b8e4072c3cee7d9c2132c
Tx public key: ab42d574785ad00e4413818daf7633fa3cb4d686d679881c28c5252b7f62a699
Timestamp: 1724844096 Timestamp [UCT]: 2024-08-28 11:21:36 Age [y:d:h:m:s]: 00:088:06:58:45
Block: 1097712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63147 RingCT/type: yes/0
Extra: 01ab42d574785ad00e4413818daf7633fa3cb4d686d679881c28c5252b7f62a699021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb5a5a835fde75fe674ab5d68cf4aaf0abf8a4b0dab1541fb6a47455fb223a16 0.600000000000 1573173 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": 1097722, "vin": [ { "gen": { "height": 1097712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb5a5a835fde75fe674ab5d68cf4aaf0abf8a4b0dab1541fb6a47455fb223a16" } } ], "extra": [ 1, 171, 66, 213, 116, 120, 90, 208, 14, 68, 19, 129, 141, 175, 118, 51, 250, 60, 180, 214, 134, 214, 121, 136, 28, 40, 197, 37, 43, 127, 98, 166, 153, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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