Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f79d839a0be17267718d90039c88397a58200b934d5d53f14054c1d89fc777dc

Tx prefix hash: 7170ed2ec25d5a9158787f6d9f3a22528ec0207b17d06d786154dc905163df01
Tx public key: 797ce08e032b9eb1656ae7e389f7f5cc129d0b1255c91d377bab1533ad45e9b0
Timestamp: 1716077137 Timestamp [UCT]: 2024-05-19 00:05:37 Age [y:d:h:m:s]: 00:237:07:38:20
Block: 1025031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169851 RingCT/type: yes/0
Extra: 01797ce08e032b9eb1656ae7e389f7f5cc129d0b1255c91d377bab1533ad45e9b00211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a5ff38e92dbca677f9ab2f2b6fcb5a0ec9e912c533a7663409efef54d38b992 0.600000000000 1491238 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": 1025041, "vin": [ { "gen": { "height": 1025031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a5ff38e92dbca677f9ab2f2b6fcb5a0ec9e912c533a7663409efef54d38b992" } } ], "extra": [ 1, 121, 124, 224, 142, 3, 43, 158, 177, 101, 106, 231, 227, 137, 247, 245, 204, 18, 157, 11, 18, 85, 201, 29, 55, 123, 171, 21, 51, 173, 69, 233, 176, 2, 17, 0, 0, 0, 3, 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